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:
// Original code
<Foo>
<Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;
v0.22.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.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 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.07.16.07.1.07.16.00.14.540.23.014.0.114.0.22.2.52.3.03.1.23.1.410.3.010.6.010.0.610.0.75.0.55.0.82.6.22.6.35.3.35.5.3Updates
@typescript-eslint/eslint-pluginfrom 7.1.0 to 7.16.0Release notes
Sourced from
@​typescript-eslint/eslint-plugin's releases.... (truncated)
Changelog
Sourced from
@​typescript-eslint/eslint-plugin's changelog.... (truncated)
Commits
e803c50chore(release): publish 7.16.07b13daefix(eslint-plugin): [restrict-template-expressions] don't report tuples if `a...3c6290dfix(eslint-plugin): [no-floating-promises] addsuggestionsto tests from #9...63d17ddfeat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)d685948feat(eslint-plugin): add support for nested namespaces to unsafe-member-acces...451e738feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new r...88dd828feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)a1a9b09chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eva...d364160docs: [class-methods-use-this] fix typo (#9494)7e2b77dfeat(rule-tester): stricter rule test validations (#9086)Updates
@typescript-eslint/parserfrom 7.1.0 to 7.16.0Release notes
Sourced from
@​typescript-eslint/parser's releases.... (truncated)
Changelog
Sourced from
@​typescript-eslint/parser's changelog.... (truncated)
Commits
e803c50chore(release): publish 7.16.02865d31chore(release): publish 7.15.0b4fe94fchore(release): publish 7.14.1dfc4469chore(release): publish 7.14.01212a8fchore(release): publish 7.13.18a178edchore(release): publish 7.13.0c9a6dd9feat(parser, typescript-estree): export withoutProjectParserOptions utility (...7e93b28chore(release): publish 7.12.02bbf656fix(types): correct typing ParserOptions (#9202)e360541chore(release): publish 7.11.0Updates
esbuildfrom 0.14.54 to 0.23.0Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
9d50680publish 0.23.0 to npmac7fd04Revert "fix #1874: node defaults to--packages=external" (#3820)626ac2cfix #3818: preserve collapsed jsx whitespace7c2eb2ehashbang syntax is part of es202380c6e6epublish 0.22.0 to npm196dcadfix #1874: node defaults to--packages=external3f57db8release notes for #353991663dbProvide API to create a custom esbuild CLI with plugins (#3539)e01c0e0also mention #3665 in release notes65711b3release notes for #3674Updates
globbyfrom 14.0.1 to 14.0.2Release notes
Sourced from globby's releases.
Commits
c00056814.0.2f600250Fix typesUpdates
karma-esbuildfrom 2.2.5 to 2.3.0Release notes
Sourced from karma-esbuild's releases.
Commits
cf1cb8f2.3.02799b2bMerge pull request #55 from handerss-tibco/esbuild-17e47863fFix tests58106adSwitch to new esbuild APIs for incremental builds4f75bf3Bump 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
litfrom 3.1.2 to 3.1.4Release notes
Sourced from lit's releases.
Changelog
Sourced from lit's changelog.
Commits
9217527Version Packages (#4663)e52271btest: upgrade chai to 5.x (#4628)700799bVersion Packages (#4625)1b00c07Update prettier (#4559)Updates
mochafrom 10.3.0 to 10.6.0Release notes
Sourced from mocha's releases.
... (truncated)
Changelog
Sourced from mocha's changelog.
... (truncated)
Commits
177732fRelease 10.6.0021aa80docs: add 10.6.0 to CHANGELOG.md528836edocs: fix month numbers in CHANGELOG.mdbb8d7b9feat: allow ^ versions for miscellaneous packages (#5154)514b83ffeat: allow ^ versions for data serialization packages (#5153)be82606feat: allow ^ versions for file matching packages (#5151)71e9fbafeat: allow ^ versions for yargs packages (#5152)38695dafeat: allow ^ versions for character encoding packages (#5150)b2a6358Release 10.5.2a3bb86ddocs: add 10.5.2 to CHANGELOG.mdUpdates
@types/mochafrom 10.0.6 to 10.0.7Commits
Updates
rimraffrom 5.0.5 to 5.0.8Commits
0d83c125.0.888e632bdrop eol node 14f8c4b20DOC: missing punctuation & some grammar fixes (#307)dc3ffe5update tap, tshy, drop node 16 from cifb974ad5.0.78ba2442engines: need 14.18, where 'node:path' shows up39340d1update depse729f765.0.64472c0eDOC: add that it is cross platform46b425fImprove readability of READMEUpdates
tslibfrom 2.6.2 to 2.6.3Release notes
Sourced from tslib's releases.
Commits
a280d4b2.6.3983d81b'await using' normative changes (#258)54cd71cBump the github-actions group with 3 updates (#253)298efd9Bump the github-actions group with 1 update (#242)e8b4418Bump the github-actions group with 1 update (#241)ae8c5c3Bump the github-actions group with 2 updates (#240)2b38d87JSDoc typo on__exportStar. (#221)8466326Bump the github-actions group with 1 update (#233)a57d986Bump the github-actions group with 1 update (#230)2bf5a06Bump the github-actions group with 2 updates (#228)Updates
typescriptfrom 5.3.3 to 5.5.3Release notes
Sourced from typescript's releases.
... (truncated)
Commits
f0e9921Bump version to 5.5.3 and LKG738bd60Cherry-pick #58966 to release-5.5 (#59002)ce2e60eUpdate 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 (#...5367ae1Bump 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