This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:
// Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')
// Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)
⚠️ WARNING ⚠️
This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:
This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.
v0.21.2
Correct this in field and accessor decorators (#3761)
This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:
This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:
// Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')
// Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)
⚠️ WARNING ⚠️
This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:
This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.
0.21.2
Correct this in field and accessor decorators (#3761)
This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:
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 show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the dev-packages group with 7 updates in the /rascal-vscode-extension directory:
7.4.0
7.10.0
7.4.0
7.10.0
2.3.9
2.3.10
2.24.0
2.26.1
0.20.2
0.21.3
5.4.3
5.4.5
7.3.2
8.2.0
Updates
@typescript-eslint/eslint-plugin
from 7.4.0 to 7.10.0Release notes
Sourced from
@typescript-eslint/eslint-plugin
's releases.... (truncated)
Changelog
Sourced from
@typescript-eslint/eslint-plugin
's changelog.... (truncated)
Commits
c18226e
chore(release): publish 7.10.08d92ba8
docs: [no-floating-promises] fix capitalization typo (#9118)d951d83
fix(eslint-plugin): [prefer-regexp-exec] fix heuristic to check whether regex...987a96e
feat(eslint-plugin): [sort-type-constituents] support case sensitive sorting ...77fc366
chore(release): publish 7.9.0f53fece
chore: add knip (#8192)8acb8d4
fix(eslint-plugin): [explicit-function-return-types] fix false positive on de...d696ea2
docs(eslint-plugin): fix several 404 URLs (#9064)37a41d9
docs: fix broken link toimport/no-duplicates
onno-duplicate-imports
pag...ab92621
docs: correct its/it's spelling (#9048)Updates
@typescript-eslint/parser
from 7.4.0 to 7.10.0Release notes
Sourced from
@typescript-eslint/parser
's releases.... (truncated)
Changelog
Sourced from
@typescript-eslint/parser
's changelog.... (truncated)
Commits
c18226e
chore(release): publish 7.10.077fc366
chore(release): publish 7.9.0f53fece
chore: add knip (#8192)ee677f6
chore(release): publish 7.8.03e19436
chore(release): publish 7.7.1e44a1a2
chore(release): publish 7.7.0e1db872
chore(release): publish 7.6.0a6ab2cb
feat: bump npm dependency ranges (#8860)a14ba9d
chore(release): publish 7.5.0ecb6b55
docs: add homepage (#8742)Updates
@vscode/test-electron
from 2.3.9 to 2.3.10Changelog
Sourced from
@vscode/test-electron
's changelog.Commits
68fb5fb
2.3.103f7a3cc
feat: runVSCodeCommand as workaround for CVE-2024-2798040ecedf
Merge pull request #263 from microsoft/dependabot/npm_and_yarn/vite-2.9.18e7b5d61
chore(deps): bump vite from 2.9.17 to 2.9.181305af5
chore(deps): updateglob
and remove@types/glob
(#262)bc400a2
Merge pull request #256 from microsoft/connor4312/fix-windows-first-run92c0591
Merge pull request #257 from microsoft/dependabot/npm_and_yarn/vite-2.9.171caf111
chore(deps): bump vite from 2.9.16 to 2.9.17Updates
@vscode/vsce
from 2.24.0 to 2.26.1Release notes
Sourced from
@vscode/vsce
's releases.... (truncated)
Commits
9316842
Merge pull request #974 from microsoft/benibenj/modest-dragonfly093d33f
Merge pull request #973 from microsoft/benibenj/hon-guineafowlc1ced1d
:lipstick:dd558a9
Remove double checkingf6eb247
:lipstick:b1bde5a
Only sanitize on windows9e06c04
:lipstick:1188664
Commit message enclose in quotes97f8b80
:lipstick:434754f
Remove unused shell-quoteUpdates
esbuild
from 0.20.2 to 0.21.3Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
efa3dd2
publish 0.21.3 to npm5e7cf25
fix #3760: implement decorator metadata proposalbd0b13b
lowering: always propagate class expression names90acd14
explicit bitwise operators for initializer flagsba548df
move decorator initializer list to after the class66b7c6d
fix #3768: bundled decorators in derived classes6e6f15f
fix #3767:tsconfig.json
files inside symlinksb7dcb95
transform: reuselowerField
for auto-accessorsb24180e
publish 0.21.2 to npmf82e0ad
fix #3761:this
in field and accessor decoratorsUpdates
typescript
from 5.4.3 to 5.4.5Release notes
Sourced from typescript's releases.
Commits
27bcd4c
Update LKG9f33bf1
🤖 Pick PR #58098 (Fix constraints of nested homomorph...) into release-5.4 (#...71b2f84
Bump version to 5.4.5 and LKG892936f
🤖 Pick PR #58083 (Don't propagate partial union/inter...) into release-5.4 (#...38a7c05
release-5.4: Always set node-version for setup-node (#58117)b754fc3
🤖 Pick PR #57778 (fix type import check for default-i...) into release-5.4 (#...8eb3367
Bump version to 5.4.4 and LKGde9096b
🤖 Pick PR #57871 (Divide-and-conquer strategy for int...) into release-5.4 (#...06aae98
🤖 Pick PR #57973 (Compare package.json paths with cor...) into release-5.4 (#...6d8134e
🤖 Pick PR #57637 (Fixed a regression related to deter...) into release-5.4 (#...Updates
vscode-extension-tester
from 7.3.2 to 8.2.0Release notes
Sourced from vscode-extension-tester's releases.
... (truncated)
Commits
0954461
chore(release): Publish v8.2.0 (#1296)35f8826
chore: Add licence headers (#1291)e941ccf
feat: Add support for VS Code 1.89.x (#1293)28702d7
build(deps): bump@vscode/vsce
from 2.26.0 to 2.26.1 (#1292)93fa189
feat: Add code coverage support (#1234)c849103
build(deps): bump selenium-webdriver from 4.19.0 to 4.20.0 (#1276)466d3c6
chore(release): Publish0fab1db
build: Improve ESLint config and fix reported errors/warnings8139dfa
build: Fix ESLint warnings for packages/extesterb230f05
build: Use ESLint for all packages during compileDependabot 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 show