Allow using the node: import prefix with es* targets (#3821)
The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)
Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.
Fix incorrect location of certain error messages (#3845)
This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)
With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.
v0.23.0
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.
Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.
I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:
Allow using the node: import prefix with es* targets (#3821)
The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)
Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.
Fix incorrect location of certain error messages (#3845)
This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)
With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.
0.23.0
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.
Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.
I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
Most Recent Ignore Conditions Applied to This Pull Request
| Dependency Name | Ignore Conditions |
| --- | --- |
| @types/node | [>= 18.a, < 19] |
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 extension-dependencies group with 10 updates in the / directory:
4.2.3
4.2.5
7.0.0
8.0.0
20.12.12
22.4.1
1.89.0
1.92.0
7.10.0
8.1.0
7.10.0
8.1.0
2.26.1
3.0.0
0.21.4
0.23.1
3.2.5
3.3.3
5.4.5
5.5.4
Updates
comment-json
from 4.2.3 to 4.2.5Commits
0f4f85a
bump version 4.2.5c92fc59
Merge pull request #46 from karlhorky/patch-1a4b8eb1
Fix npm TypeScript icon6e774bb
#45: bump version 4.2.402de76e
Merge pull request #45 from karlhorky/patch-12175d24
Fix type for parse()4416b4d
README.md: update badgea72016b
test: goodbye travis, hello github9671f1b
Merge pull request #40 from ambujsahu81/patch-18fe85ca
Fix query comments example in readme.mdUpdates
promise-socket
from 7.0.0 to 8.0.0Release notes
Sourced from promise-socket's releases.
Changelog
Sourced from promise-socket's changelog.
Commits
b786a15
Update dependency promise-duplex to v89cebd7f
Improved exampled218628
Renovate: Typescript updates are always separate0a072d2
Changelog for #631b4899c
setTimeout
returnsthis
440fbf6
promisify2f509d5
Converted to ESM moduleUpdates
@types/node
from 20.12.12 to 22.4.1Commits
Updates
@types/vscode
from 1.89.0 to 1.92.0Commits
Updates
@typescript-eslint/eslint-plugin
from 7.10.0 to 8.1.0Release notes
Sourced from
@typescript-eslint/eslint-plugin
's releases.... (truncated)
Changelog
Sourced from
@typescript-eslint/eslint-plugin
's changelog.... (truncated)
Commits
3d78392
chore(release): publish 8.1.0abe351d
fix(eslint-plugin): [no-unnecessary-type-parameters] clarify message (#9737)6a1c177
feat(eslint-plugin): [no-misused-promises] check subtype methods against heri...fc3ba92
fix(eslint-plugin): [prefer-optional-chain] wrong parenthesis fix output (#9597)c20bd2f
feat(eslint-plugin): [no-unsafe-return] check promise any (#8693)3d9ae44
fix(eslint-plugin): [member-ordering] get accessor member name & take into ac...fe56157
fix(eslint-plugin): [no-unnecessary-type-parameters] skip checking function b...278697f
fix(eslint-plugin): [no-unsafe-enum-comparison] typo in test (#9779)a4992ff
feat(typescript-estree): restrict variable declarator definite/init combinati...a26e3c7
chore: enable prefer-regexp-test (#9658)Updates
@typescript-eslint/parser
from 7.10.0 to 8.1.0Release notes
Sourced from
@typescript-eslint/parser
's releases.... (truncated)
Changelog
Sourced from
@typescript-eslint/parser
's changelog.... (truncated)
Commits
3d78392
chore(release): publish 8.1.0a26e3c7
chore: enable prefer-regexp-test (#9658)e05c2e5
chore(release): publish 8.0.11db993a
chore(release): publish 8.0.01b0468e
Merge branch 'main'35cf3d2
chore(release): publish 7.18.0f3dfc0a
Merge branch 'main' into v805c9cb8
chore(release): publish 7.17.0ae980e3
Merge branch 'main'58be99f
chore: enable prefer-object-spread (#9541)Updates
@vscode/vsce
from 2.26.1 to 3.0.0Release notes
Sourced from
@vscode/vsce
's releases.... (truncated)
Commits
f7ed2e1
Merge pull request #1035 from microsoft/benibenj/accessible-wolf6b64546
engine updatece9b369
update depricated dependencies and move to node 20b347c2b
Merge pull request #1034 from microsoft/benibenj/revertDependency784e74d
Revert "update depricated dependencies"b10ae0b
fix: probabilistic trigger v8 crash (#1032)cf0bc32
Merge pull request #1028 from microsoft/dev/bhavyau/need-more-info71d485d
Remove need-more-info-closer workflowca8fa40
Merge pull request #1027 from microsoft/benibenj/logical-duckd0e1a5c
update depricated dependenciesUpdates
esbuild
from 0.21.4 to 0.23.1Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
3327274
publish 0.23.1 to npm38e22ed
add a warning/debug log message for #3867a15bb51
fix #3825: memory leak ofpluginData
valuesf6e6481
fix #3838: print comments beforecase
clauses9c13ae1
fix #3853: update go 1.22.4 => 1.22.578f89e4
fix #3845: some incorrect error message locations892d2a7
fix #3834: cli sometimes panics with--analyze
360d472
fix a typo in the release notese3f4e2d
fix #3821: allownode:
prefix withes*
targets9d50680
publish 0.23.0 to npmUpdates
prettier
from 3.2.5 to 3.3.3Release notes
Sourced from prettier's releases.
Changelog
Sourced from prettier's changelog.
... (truncated)
Commits
5282938
Release 3.3.39102b73
Add parentheses for decorator expressions (#16458)6bbd461
chore(deps): update eslint related dependencies (#16478)04b560f
chore(deps): update dependency browserslist to v4.23.2 (#16475)614f070
chore(deps): update typescript-eslint to v8.0.0-alpha.41 (#16477)d59a15d
chore(deps): update dependency npm-run-all2 to v6.2.2 (#16476)5ca2fc9
Support Angular@let
declaration syntax (#16474)bfcfdcc
chore(deps): update babel to v7.24.8 (#16472)977c161
chore(deps): update dependency acorn to v8.12.1 (#16464)550606e
chore(deps): update babel to v7.24.8 (#16470)Updates
typescript
from 5.4.5 to 5.5.4Release notes
Sourced from typescript's releases.
... (truncated)
Commits
c8a7d58
Bump version to 5.5.4 and LKGc0ded04
🤖 Pick PR #58771 (Allow references to the global Symb...) into release-5.5 (#...5ba41e2
🤖 Pick PR #59208 (Write non-missing undefined on mapp...) into release-5.5 (#...b075332
🤖 Pick PR #59337 (Allow declarationMap to be emitted ...) into release-5.5 (#...9dd6f91
Cherry-pick "Stop using latest Node in CI" to release-5.5 (#59348)bf0ddaf
🤖 Pick PR #59070 (Delay the calculation of common sou...) into release-5.5 (#...a44e2d9
🤖 Pick PR #59160 (Fixed crash on authored import type...) into release-5.5 (#...f35206d
🤖 Pick PR #59325 (Don't skip markLinkedReferences on ...) into release-5.5 (#...1109550
Fix baselines on release-5.5 (#59330)8794318
🤖 Pick PR #59215 (Fix codefix crash on circular alias...) into release-5.5 (#...Most Recent Ignore Conditions Applied to This Pull Request
| Dependency Name | Ignore Conditions | | --- | --- | | @types/node | [>= 18.a, < 19] |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