Milo123459

Milo123459

being unproductive

Member Since 2 years ago

London, UK

Experience Points
168
follower
Lessons Completed
27
follow
Lessons Completed
575
stars
Best Reply Awards
143
repos

4348 contributions in the last year

Pinned
⚡ 🌌⭐ Git tooling of the future.
⚡ 🤙 Vext is a code editor that lives in the Terminal.
⚡ A CLI-based task manager written in Rust.
Activity
Nov
29
1 day ago
Activity icon
fork

Milo123459 forked advaith1/rollouts

⚡ React and Next.js site to display Discord server experiments and their rollouts
Milo123459 Updated
fork time in 5 hours ago
started
started time in 6 hours ago
started
started time in 9 hours ago
Activity icon
delete

Milo123459 in Milo123459/glitter delete branch dependabot/cargo/anyhow-1.0.50

deleted time in 10 hours ago
push

Milo123459 push Milo123459/glitter

Milo123459
Milo123459

chore: bump anyhow from 1.0.49 to 1.0.50

Bumps anyhow from 1.0.49 to 1.0.50.


updated-dependencies:

  • dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] [email protected]

Milo123459
Milo123459

Merge pull request #50 from Milo123459/dependabot/cargo/anyhow-1.0.50

commit sha: b56778fc6165b11534b009d170dd6191e1e6bc85

push time in 10 hours ago
pull request

Milo123459 pull request Milo123459/glitter

Milo123459
Milo123459

chore: bump anyhow from 1.0.49 to 1.0.50

Bumps anyhow from 1.0.49 to 1.0.50.

Release notes

Sourced from anyhow's releases.

1.0.50

Commits
  • 7f5c9c4 Release 1.0.50
  • 865de15 Merge pull request #206 from dtolnay/pat
  • da5c3fd Add pattern tests
  • e1dcc49 Pattern parser to preserve all spans in if let and for
  • b577cd9 Refer to concat and stringify macros by absolute path
  • 68d1f4c Merge pull request #205 from dtolnay/traitobject
  • 04732a7 Parse trait object types
  • 11d3eb7 Merge pull request #204 from dtolnay/assoc
  • 6f18821 Parse associated type constraints in dyn trait object types
  • 210d741 Merge pull request #203 from dtolnay/fn
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
started
started time in 19 hours ago
pull request

Milo123459 pull request Milo123459/website

Milo123459
Milo123459

Bump esbuild from 0.13.15 to 0.14.0

Bumps esbuild from 0.13.15 to 0.14.0.

Release notes

Sourced from esbuild's releases.

v0.14.0

This release contains backwards-incompatible changes. Since esbuild is before version 1.0.0, these changes have been released as a new minor version to reflect this (as recommended by npm). You should either be pinning the exact version of esbuild in your package.json file or be using a version range syntax that only accepts patch upgrades such as ~0.13.0. See the documentation about semver for more information.

  • Add support for TypeScript's preserveValueImports setting (#1525)

    TypeScript 4.5, which was just released, added a new setting called preserveValueImports. This release of esbuild implements support for this new setting. However, this release also changes esbuild's behavior regarding the importsNotUsedAsValues setting, so this release is being considered a breaking change. Now esbuild's behavior should more accurately match the behavior of the TypeScript compiler. This is described in more detail below.

    The difference in behavior is around unused imports. By default, unused import names are considered to be types and are completely removed if they are unused. If all import names are removed for a given import statement, then the whole import statement is removed too. The two tsconfig.json settings importsNotUsedAsValues and preserveValueImports let you customize this. Here's what the TypeScript compiler's output looks like with these different settings enabled:

    // Original code
    import { unused } from "foo";
    

    // Default output /* (the import is completely removed) */

    // Output with "importsNotUsedAsValues": "preserve" import "foo";

    // Output with "preserveValueImports": true import { unused } from "foo";

    Previously, since the preserveValueImports setting didn't exist yet, esbuild had treated the importsNotUsedAsValues setting as if it were what is now the preserveValueImports setting instead. This was a deliberate deviation from how the TypeScript compiler behaves, but was necessary to allow esbuild to be used as a TypeScript-to-JavaScript compiler inside of certain composite languages such as Svelte and Vue. These languages append additional code after converting the TypeScript to JavaScript so unused imports may actually turn out to be used later on:

    <script>
    import { someFunc } from "./some-module.js";
    </script>
    <button on:click={someFunc}>Click me!</button>
    

    Previously the implementers of these languages had to use the importsNotUsedAsValues setting as a hack for esbuild to preserve the import statements. With this release, esbuild now follows the behavior of the TypeScript compiler so implementers will need to use the new preserveValueImports setting to do this instead. This is the breaking change.

  • TypeScript code follows JavaScript class field semantics with --target=esnext (#1480)

    TypeScript 4.3 included a subtle breaking change that wasn't mentioned in the TypeScript 4.3 blog post: class fields will now be compiled with different semantics if "target": "ESNext" is present in tsconfig.json. Specifically in this case useDefineForClassFields will default to true when not specified instead of false. This means class field behavior in TypeScript code will now match JavaScript instead of doing something else:

    class Base {
      set foo(value) { console.log('set', value) }
    }
    class Derived extends Base {
      foo = 123
    }
    new Derived()
    

    In TypeScript 4.2 and below, the TypeScript compiler would generate code that prints set 123 when tsconfig.json contains "target": "ESNext" but in TypeScript 4.3 and above, the TypeScript compiler will now generate code that doesn't print anything. This is the difference between "assign" semantics and "define" semantics.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.0

This release contains backwards-incompatible changes. Since esbuild is before version 1.0.0, these changes have been released as a new minor version to reflect this (as recommended by npm). You should either be pinning the exact version of esbuild in your package.json file or be using a version range syntax that only accepts patch upgrades such as ~0.13.0. See the documentation about semver for more information.

  • Add support for TypeScript's preserveValueImports setting (#1525)

    TypeScript 4.5, which was just released, added a new setting called preserveValueImports. This release of esbuild implements support for this new setting. However, this release also changes esbuild's behavior regarding the importsNotUsedAsValues setting, so this release is being considered a breaking change. Now esbuild's behavior should more accurately match the behavior of the TypeScript compiler. This is described in more detail below.

    The difference in behavior is around unused imports. By default, unused import names are considered to be types and are completely removed if they are unused. If all import names are removed for a given import statement, then the whole import statement is removed too. The two tsconfig.json settings importsNotUsedAsValues and preserveValueImports let you customize this. Here's what the TypeScript compiler's output looks like with these different settings enabled:

    // Original code
    import { unused } from "foo";
    

    // Default output /* (the import is completely removed) */

    // Output with "importsNotUsedAsValues": "preserve" import "foo";

    // Output with "preserveValueImports": true import { unused } from "foo";

    Previously, since the preserveValueImports setting didn't exist yet, esbuild had treated the importsNotUsedAsValues setting as if it were what is now the preserveValueImports setting instead. This was a deliberate deviation from how the TypeScript compiler behaves, but was necessary to allow esbuild to be used as a TypeScript-to-JavaScript compiler inside of certain composite languages such as Svelte and Vue. These languages append additional code after converting the TypeScript to JavaScript so unused imports may actually turn out to be used later on:

    <script>
    import { someFunc } from "./some-module.js";
    </script>
    <button on:click={someFunc}>Click me!</button>
    

    Previously the implementers of these languages had to use the importsNotUsedAsValues setting as a hack for esbuild to preserve the import statements. With this release, esbuild now follows the behavior of the TypeScript compiler so implementers will need to use the new preserveValueImports setting to do this instead. This is the breaking change.

  • TypeScript code follows JavaScript class field semantics with --target=esnext (#1480)

    TypeScript 4.3 included a subtle breaking change that wasn't mentioned in the TypeScript 4.3 blog post: class fields will now be compiled with different semantics if "target": "ESNext" is present in tsconfig.json. Specifically in this case useDefineForClassFields will default to true when not specified instead of false. This means class field behavior in TypeScript code will now match JavaScript instead of doing something else:

    class Base {
      set foo(value) { console.log('set', value) }
    }
    class Derived extends Base {
      foo = 123
    }
    new Derived()
    

    In TypeScript 4.2 and below, the TypeScript compiler would generate code that prints set 123 when tsconfig.json contains "target": "ESNext" but in TypeScript 4.3 and above, the TypeScript compiler will now generate code that doesn't print anything. This is the difference between "assign" semantics and "define" semantics.

... (truncated)

Commits
  • 45bcd8e publish 0.14.0 to npm
  • 731f559 change output for top-level TypeScript enums
  • dabf3b7 ts: fix "this" inside class inside namespace
  • 8569cdf fix #1803: panic with invalid "@​import" conditions
  • 366dacd ts: use => instead of function for enum/namespace
  • 1c277e3 ts: forbid "this" inside "namespace" and "enum"
  • d0b0874 fix #1791: mark certain "Set" and "Map" as pure
  • 1084849 ts enum: avoid merging siblings in nested blocks
  • 2816a99 fix #1796: fix legal comment parsing in css
  • 0e85bef rename license => legal
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
push

Milo123459 push Milo123459/website

Milo123459
Milo123459

Bump esbuild from 0.13.15 to 0.14.0

Bumps esbuild from 0.13.15 to 0.14.0.


updated-dependencies:

  • dependency-name: esbuild dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] [email protected]

Milo123459
Milo123459

Merge pull request #245 from Milo123459/dependabot/npm_and_yarn/esbuild-0.14.0

commit sha: 7882c941571ca9ec05e6c07fc38e8e2dd5659255

push time in 19 hours ago
Activity icon
delete

Milo123459 in Milo123459/website delete branch dependabot/npm_and_yarn/esbuild-0.14.0

deleted time in 19 hours ago
Activity icon
delete

Milo123459 in Milo123459/website delete branch dependabot/npm_and_yarn/types/react-17.0.37

deleted time in 19 hours ago
push

Milo123459 push Milo123459/website

Milo123459
Milo123459

Bump @types/react from 17.0.36 to 17.0.37

Bumps @types/react from 17.0.36 to 17.0.37.


updated-dependencies:

  • dependency-name: "@types/react" dependency-type: direct:development update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] [email protected]

Milo123459
Milo123459

Merge pull request #242 from Milo123459/dependabot/npm_and_yarn/types/react-17.0.37

commit sha: 1d0e021dc45adccdbfef1c2b1258209bafadbd28

push time in 19 hours ago
pull request

Milo123459 pull request Milo123459/website

Milo123459
Milo123459

Bump @types/react from 17.0.36 to 17.0.37

Bumps @types/react from 17.0.36 to 17.0.37.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
pull request

Milo123459 pull request Milo123459/website

Milo123459
Milo123459

Bump preact from 10.5.15 to 10.6.1

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps preact from 10.5.15 to 10.6.1.

Release notes

Sourced from preact's releases.

10.6.1

Fixes

Maintenance

10.6.0

Types

Fixes

Maintenance

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Activity icon
delete

Milo123459 in Milo123459/website delete branch dependabot/npm_and_yarn/react-query-3.33.7

deleted time in 19 hours ago
push

Milo123459 push Milo123459/website

Milo123459
Milo123459

Bump react-query from 3.33.4 to 3.33.7

Bumps react-query from 3.33.4 to 3.33.7.


updated-dependencies:

  • dependency-name: react-query dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] [email protected]

Milo123459
Milo123459

Merge pull request #246 from Milo123459/dependabot/npm_and_yarn/react-query-3.33.7

commit sha: c8831359bc3c9384926f9215069222a28152bb67

push time in 19 hours ago
pull request

Milo123459 pull request Milo123459/website

Milo123459
Milo123459

Bump react-query from 3.33.4 to 3.33.7

Bumps react-query from 3.33.4 to 3.33.7.

Release notes

Sourced from react-query's releases.

v3.33.7

3.33.7 (2021-11-28)

Bug Fixes

  • useQuery: continue retries if query unmounts and remounts (#3032) (dc2df10)

v3.33.6

3.33.6 (2021-11-26)

Bug Fixes

  • useQueries: search for unused observers if keepPreviousData (#2680) (#2866) (c51498a)

v3.33.5

3.33.5 (2021-11-24)

Bug Fixes

  • useQueries: add useMemo to useQueries to keep result stable (#2992) (c6906b3)
Commits
  • dc2df10 fix(useQuery): continue retries if query unmounts and remounts (#3032)
  • c51498a fix(useQueries): search for unused observers if keepPreviousData (#2680) (#2866)
  • c6906b3 fix(useQueries): add useMemo to useQueries to keep result stable (#2992)
  • f18881d docs: add pitfalls section for window focus refetching (#3018)
  • 9114774 docs(query-keys guide): change "And" to "An" (#3010)
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Activity icon
issue

Milo123459 issue comment Milo123459/website

Milo123459
Milo123459

Bump esbuild from 0.13.15 to 0.14.0

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps esbuild from 0.13.15 to 0.14.0.

Release notes

Sourced from esbuild's releases.

v0.14.0

This release contains backwards-incompatible changes. Since esbuild is before version 1.0.0, these changes have been released as a new minor version to reflect this (as recommended by npm). You should either be pinning the exact version of esbuild in your package.json file or be using a version range syntax that only accepts patch upgrades such as ~0.13.0. See the documentation about semver for more information.

  • Add support for TypeScript's preserveValueImports setting (#1525)

    TypeScript 4.5, which was just released, added a new setting called preserveValueImports. This release of esbuild implements support for this new setting. However, this release also changes esbuild's behavior regarding the importsNotUsedAsValues setting, so this release is being considered a breaking change. Now esbuild's behavior should more accurately match the behavior of the TypeScript compiler. This is described in more detail below.

    The difference in behavior is around unused imports. By default, unused import names are considered to be types and are completely removed if they are unused. If all import names are removed for a given import statement, then the whole import statement is removed too. The two tsconfig.json settings importsNotUsedAsValues and preserveValueImports let you customize this. Here's what the TypeScript compiler's output looks like with these different settings enabled:

    // Original code
    import { unused } from "foo";
    

    // Default output /* (the import is completely removed) */

    // Output with "importsNotUsedAsValues": "preserve" import "foo";

    // Output with "preserveValueImports": true import { unused } from "foo";

    Previously, since the preserveValueImports setting didn't exist yet, esbuild had treated the importsNotUsedAsValues setting as if it were what is now the preserveValueImports setting instead. This was a deliberate deviation from how the TypeScript compiler behaves, but was necessary to allow esbuild to be used as a TypeScript-to-JavaScript compiler inside of certain composite languages such as Svelte and Vue. These languages append additional code after converting the TypeScript to JavaScript so unused imports may actually turn out to be used later on:

    <script>
    import { someFunc } from "./some-module.js";
    </script>
    <button on:click={someFunc}>Click me!</button>
    

    Previously the implementers of these languages had to use the importsNotUsedAsValues setting as a hack for esbuild to preserve the import statements. With this release, esbuild now follows the behavior of the TypeScript compiler so implementers will need to use the new preserveValueImports setting to do this instead. This is the breaking change.

  • TypeScript code follows JavaScript class field semantics with --target=esnext (#1480)

    TypeScript 4.3 included a subtle breaking change that wasn't mentioned in the TypeScript 4.3 blog post: class fields will now be compiled with different semantics if "target": "ESNext" is present in tsconfig.json. Specifically in this case useDefineForClassFields will default to true when not specified instead of false. This means class field behavior in TypeScript code will now match JavaScript instead of doing something else:

    class Base {
      set foo(value) { console.log('set', value) }
    }
    class Derived extends Base {
      foo = 123
    }
    new Derived()
    

    In TypeScript 4.2 and below, the TypeScript compiler would generate code that prints set 123 when tsconfig.json contains "target": "ESNext" but in TypeScript 4.3 and above, the TypeScript compiler will now generate code that doesn't print anything. This is the difference between "assign" semantics and "define" semantics.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.0

This release contains backwards-incompatible changes. Since esbuild is before version 1.0.0, these changes have been released as a new minor version to reflect this (as recommended by npm). You should either be pinning the exact version of esbuild in your package.json file or be using a version range syntax that only accepts patch upgrades such as ~0.13.0. See the documentation about semver for more information.

  • Add support for TypeScript's preserveValueImports setting (#1525)

    TypeScript 4.5, which was just released, added a new setting called preserveValueImports. This release of esbuild implements support for this new setting. However, this release also changes esbuild's behavior regarding the importsNotUsedAsValues setting, so this release is being considered a breaking change. Now esbuild's behavior should more accurately match the behavior of the TypeScript compiler. This is described in more detail below.

    The difference in behavior is around unused imports. By default, unused import names are considered to be types and are completely removed if they are unused. If all import names are removed for a given import statement, then the whole import statement is removed too. The two tsconfig.json settings importsNotUsedAsValues and preserveValueImports let you customize this. Here's what the TypeScript compiler's output looks like with these different settings enabled:

    // Original code
    import { unused } from "foo";
    

    // Default output /* (the import is completely removed) */

    // Output with "importsNotUsedAsValues": "preserve" import "foo";

    // Output with "preserveValueImports": true import { unused } from "foo";

    Previously, since the preserveValueImports setting didn't exist yet, esbuild had treated the importsNotUsedAsValues setting as if it were what is now the preserveValueImports setting instead. This was a deliberate deviation from how the TypeScript compiler behaves, but was necessary to allow esbuild to be used as a TypeScript-to-JavaScript compiler inside of certain composite languages such as Svelte and Vue. These languages append additional code after converting the TypeScript to JavaScript so unused imports may actually turn out to be used later on:

    <script>
    import { someFunc } from "./some-module.js";
    </script>
    <button on:click={someFunc}>Click me!</button>
    

    Previously the implementers of these languages had to use the importsNotUsedAsValues setting as a hack for esbuild to preserve the import statements. With this release, esbuild now follows the behavior of the TypeScript compiler so implementers will need to use the new preserveValueImports setting to do this instead. This is the breaking change.

  • TypeScript code follows JavaScript class field semantics with --target=esnext (#1480)

    TypeScript 4.3 included a subtle breaking change that wasn't mentioned in the TypeScript 4.3 blog post: class fields will now be compiled with different semantics if "target": "ESNext" is present in tsconfig.json. Specifically in this case useDefineForClassFields will default to true when not specified instead of false. This means class field behavior in TypeScript code will now match JavaScript instead of doing something else:

    class Base {
      set foo(value) { console.log('set', value) }
    }
    class Derived extends Base {
      foo = 123
    }
    new Derived()
    

    In TypeScript 4.2 and below, the TypeScript compiler would generate code that prints set 123 when tsconfig.json contains "target": "ESNext" but in TypeScript 4.3 and above, the TypeScript compiler will now generate code that doesn't print anything. This is the difference between "assign" semantics and "define" semantics.

... (truncated)

Commits
  • 45bcd8e publish 0.14.0 to npm
  • 731f559 change output for top-level TypeScript enums
  • dabf3b7 ts: fix "this" inside class inside namespace
  • 8569cdf fix #1803: panic with invalid "@​import" conditions
  • 366dacd ts: use => instead of function for enum/namespace
  • 1c277e3 ts: forbid "this" inside "namespace" and "enum"
  • d0b0874 fix #1791: mark certain "Set" and "Map" as pure
  • 1084849 ts enum: avoid merging siblings in nested blocks
  • 2816a99 fix #1796: fix legal comment parsing in css
  • 0e85bef rename license => legal
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Activity icon
delete

Milo123459 in Milo123459/website delete branch dependabot/npm_and_yarn/prettier-2.5.0

deleted time in 19 hours ago
push

Milo123459 push Milo123459/website

Milo123459
Milo123459

Bump prettier from 2.4.1 to 2.5.0

Bumps prettier from 2.4.1 to 2.5.0.


updated-dependencies:

  • dependency-name: prettier dependency-type: direct:development update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] [email protected]

Milo123459
Milo123459

Merge pull request #244 from Milo123459/dependabot/npm_and_yarn/prettier-2.5.0

commit sha: c243531e69d8e41836f17e4d6ab4ba0059332ed8

push time in 19 hours ago
pull request

Milo123459 pull request Milo123459/website

Milo123459
Milo123459

Bump prettier from 2.4.1 to 2.5.0

Bumps prettier from 2.4.1 to 2.5.0.

Release notes

Sourced from prettier's releases.

2.5.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

2.5.0

diff

🔗 Release Notes

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Activity icon
issue

Milo123459 issue comment Milo123459/website

Milo123459
Milo123459

Bump @types/react from 17.0.36 to 17.0.37

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps @types/react from 17.0.36 to 17.0.37.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Activity icon
delete

Milo123459 in Milo123459/website delete branch dependabot/npm_and_yarn/framer-motion-5.3.3

deleted time in 19 hours ago
push

Milo123459 push Milo123459/website

Milo123459
Milo123459

Bump framer-motion from 5.3.1 to 5.3.3

Bumps framer-motion from 5.3.1 to 5.3.3.


updated-dependencies:

  • dependency-name: framer-motion dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] suppor[email protected]

Milo123459
Milo123459

Merge pull request #241 from Milo123459/dependabot/npm_and_yarn/framer-motion-5.3.3

commit sha: 67eadcbefe4e3553794c6f3ee2c25ae94e08d105

push time in 19 hours ago
pull request

Milo123459 pull request Milo123459/website

Milo123459
Milo123459

Bump framer-motion from 5.3.1 to 5.3.3

Bumps framer-motion from 5.3.1 to 5.3.3.

Changelog

Sourced from framer-motion's changelog.

[5.3.3] 2021-11-24

Fixed

  • Fixing animating to CSS variables with SVGElement. Issue
  • Unsetting z-index for resting Reorder.Item components. Issue
  • Forward native drag listeners to draggable elements. Issue
  • Authors can now support browsers without Proxy by using motion("div") syntax. Issue

[5.3.2] 2021-11-23

Fixed

  • Ensuring forced renders are batched so sibling AnimatePresence renders are triggered together. Issue
  • Viewport enter/leave event handlers are passed IntersectionObserverEntry or null if IntersectionObserver is not supported on the device. Issue
  • No longer applying touch scroll-disabling styles if dragListener is set to false. Issue
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Activity icon
delete

Milo123459 in Milo123459/website delete branch dependabot/npm_and_yarn/types/node-16.11.10

deleted time in 19 hours ago
push

Milo123459 push Milo123459/website

Milo123459
Milo123459

Bump @types/node from 16.11.9 to 16.11.10

Bumps @types/node from 16.11.9 to 16.11.10.


updated-dependencies:

  • dependency-name: "@types/node" dependency-type: direct:development update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] [email protected]

Milo123459
Milo123459

Merge pull request #239 from Milo123459/dependabot/npm_and_yarn/types/node-16.11.10

commit sha: 08103ea9b31863f612f9da85f03a6d8b5d0c86ea

push time in 19 hours ago
pull request

Milo123459 pull request Milo123459/website

Milo123459
Milo123459

Bump @types/node from 16.11.9 to 16.11.10

Bumps @types/node from 16.11.9 to 16.11.10.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Nov
28
2 days ago
Activity icon
created tag
createdAt 1 day ago
Previous