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.21.0 or ~0.21.0. See npm's documentation about semver for more information.
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.
With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.
The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
This release drops support for the following operating systems:
Windows 7
Windows 8
Windows Server 2008
Windows Server 2012
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.
Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version
In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).
Update await using behavior to match TypeScript
TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.
Allow es2024 as a target environment
The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.
Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)
With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.
Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)
The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).
This changelog documents all esbuild versions published in the year 2022 (versions 0.14.11 through 0.16.12).
0.16.12
Loader defaults to js for extensionless files (#2776)
Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:
In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.
0.16.11
Avoid a syntax error in the presence of direct eval (#2761)
The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:
// Original code
if (true) {
function foo() {}
console.log(!!foo)
foo = null
console.log(!!foo)
}
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-deps group with 11 updates in the / directory:
7.1.0
7.15.0
7.1.0
7.15.0
0.14.54
0.22.0
14.0.1
14.0.2
2.2.5
2.3.0
3.1.2
3.1.4
10.3.0
10.5.2
10.0.6
10.0.7
5.0.5
5.0.7
2.6.2
2.6.3
5.3.3
5.5.3
Updates
@typescript-eslint/eslint-plugin
from 7.1.0 to 7.15.0Release notes
Sourced from
@​typescript-eslint/eslint-plugin
's releases.... (truncated)
Changelog
Sourced from
@​typescript-eslint/eslint-plugin
's changelog.... (truncated)
Commits
2865d31
chore(release): publish 7.15.02671de5
feat(eslint-plugin): back-port new rules around empty object types from v8 (#...05142c5
fix(eslint-plugin): [no-unsafe-call] differentiate a types-error any from a t...a466e07
fix: disableEXPERIMENTAL_useProjectService
indisabled-type-checked
shar...3694d8f
fix(eslint-plugin): [no-unsafe-return] differentiate a types-error any from a...9dba021
feat(eslint-plugin): [array-type] detectReadonly\<string[]>
case (#8752)b4fe94f
chore(release): publish 7.14.1f29150f
fix(eslint-plugin): [prefer-nullish-coalescing] ensure ternary fix does not r...9b7731d
fix(eslint-plugin): [prefer-nullish-coalescing] treat enums and literals as t...dfc4469
chore(release): publish 7.14.0Updates
@typescript-eslint/parser
from 7.1.0 to 7.15.0Release notes
Sourced from
@​typescript-eslint/parser
's releases.... (truncated)
Changelog
Sourced from
@​typescript-eslint/parser
's changelog.... (truncated)
Commits
2865d31
chore(release): publish 7.15.0b4fe94f
chore(release): publish 7.14.1dfc4469
chore(release): publish 7.14.01212a8f
chore(release): publish 7.13.18a178ed
chore(release): publish 7.13.0c9a6dd9
feat(parser, typescript-estree): export withoutProjectParserOptions utility (...7e93b28
chore(release): publish 7.12.02bbf656
fix(types): correct typing ParserOptions (#9202)e360541
chore(release): publish 7.11.0c18226e
chore(release): publish 7.10.0Updates
esbuild
from 0.14.54 to 0.22.0Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
80c6e6e
publish 0.22.0 to npm196dcad
fix #1874: node defaults to--packages=external
3f57db8
release notes for #353991663db
Provide API to create a custom esbuild CLI with plugins (#3539)e01c0e0
also mention #3665 in release notes65711b3
release notes for #367463eb814
Add OpenBSD arm64 (#3674)b722000
fix #3300, fix #3779: add@esbuild/wasi-preview1
6679ec8
fix: verbose analyse output improperly trimmed (#3785)94f09ea
fix #3790: warn about incorrectonResolve
pluginUpdates
globby
from 14.0.1 to 14.0.2Release notes
Sourced from globby's releases.
Commits
c000568
14.0.2f600250
Fix typesUpdates
karma-esbuild
from 2.2.5 to 2.3.0Release notes
Sourced from karma-esbuild's releases.
Commits
cf1cb8f
2.3.02799b2b
Merge pull request #55 from handerss-tibco/esbuild-17e47863f
Fix tests58106ad
Switch to new esbuild APIs for incremental builds4f75bf3
Bump esbuild to 0.17 and update peerDependenciesMaintainer changes
This version was pushed to npm by jridgewell, a new releaser for karma-esbuild since your current version.
Updates
lit
from 3.1.2 to 3.1.4Release notes
Sourced from lit's releases.
Changelog
Sourced from lit's changelog.
Commits
9217527
Version Packages (#4663)e52271b
test: upgrade chai to 5.x (#4628)700799b
Version Packages (#4625)1b00c07
Update prettier (#4559)Updates
mocha
from 10.3.0 to 10.5.2Release notes
Sourced from mocha's releases.
... (truncated)
Changelog
Sourced from mocha's changelog.
... (truncated)
Commits
b2a6358
Release 10.5.2a3bb86d
docs: add 10.5.2 to CHANGELOG.md02c04c4
fix: better tracking of seen objects in error serialization (#5032)103c56b
Release v10.5.1545b66d
docs: add 10.5.1 to CHANGELOG.mddbe229d
fix: Add error handling for nonexistent file case with --file option (#5086)b9ce511
Release v10.5.012c88a7
Docs: add 10.5.0 to CHANGELOG.mdb6aa7e8
chore: rename 'master' to 'main' in docs and tooling (#5130)67a8124
fix: include stack in browser uncaught error reporting (#5107)Updates
@types/mocha
from 10.0.6 to 10.0.7Commits
Updates
rimraf
from 5.0.5 to 5.0.7Commits
fb974ad
5.0.78ba2442
engines: need 14.18, where 'node:path' shows up39340d1
update depse729f76
5.0.64472c0e
DOC: add that it is cross platform46b425f
Improve readability of READMEa3b93ed
update deps, format codesd2fa213
update devDepsf3b2bf1
Upgrade GitHub Actions81c631e
remove FUNDING.yml (coming from .github repo now)Updates
tslib
from 2.6.2 to 2.6.3Release notes
Sourced from tslib's releases.
Commits
a280d4b
2.6.3983d81b
'await using' normative changes (#258)54cd71c
Bump the github-actions group with 3 updates (#253)298efd9
Bump the github-actions group with 1 update (#242)e8b4418
Bump the github-actions group with 1 update (#241)ae8c5c3
Bump the github-actions group with 2 updates (#240)2b38d87
JSDoc typo on__exportStar
. (#221)8466326
Bump the github-actions group with 1 update (#233)a57d986
Bump the github-actions group with 1 update (#230)2bf5a06
Bump the github-actions group with 2 updates (#228)Updates
typescript
from 5.3.3 to 5.5.3Release notes
Sourced from typescript's releases.
... (truncated)
Commits
f0e9921
Bump version to 5.5.3 and LKG738bd60
Cherry-pick #58966 to release-5.5 (#59002)ce2e60e
Update LKGf3b21a2
🤖 Pick PR #58931 (Defer creation of barebonesLibSourc...) into release-5.5 (#...7b1620b
🤖 Pick PR #58811 (fix(58801): "Move to file" on globa...) into release-5.5 (#...5367ae1
Bump version to 5.5.2 and LKG02132e5
🤖 Pick PR #58895 (Fix global when typescript.js loade...) into release-5.5 (#...45b1e3c
🤖 Pick PR #58872 (Fix declaration emit crash) into release-5.5 (#58874)17933ee
🤖 Pick PR #58810 (Fixed declaration emit issue relate...) into release-5.5 (#...552b07e
🤖 Pick PR #58786 (Fixed declaration emit crash relate...) into release-5.5 (#...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