[Snyk] Upgrade esbuild from 0.15.18 to 0.24.0 #335

X-oss-byte · 2024-10-18T17:13:26Z

Snyk has created this PR to upgrade esbuild from 0.15.18 to 0.24.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 85 versions ahead of your current version.
The recommended version was released a month ago, on 2024-09-22.

Release notes

Package name: esbuild

0.24.0 - 2024-09-22
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.23.0 or ~0.23.0. See npm's documentation about semver for more information.
- Drop support for older platforms (#3902)
  
  This release drops support for the following operating system:
  - macOS 10.15 Catalina
  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.
  
  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.23). That might look something like this:
```
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
```
- Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)
  
  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.
- Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)
  
  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.
- Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)
  
  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.
- Work around more issues with Deno 1.31+ (#3917)
  
  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.
  
  This fix was contributed by @ Joshix-1.
0.23.1 - 2024-08-16
- 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).
- Fix a memory leak with pluginData (#3825)
  
  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 - 2024-07-02
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.
- Fix preserving collapsed JSX whitespace (#3818)
  
  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>;
0.22.0 - 2024-06-30
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.
- Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
  
  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).
- Drop support for older platforms (#3802)
  
  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.
  
  This was contributed by @ ikmckenz.
- 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).
  
  Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.
  
  This release publishes esbuild precompiled for WASI preview 1 to the @ esbuild/wasi-preview1 package on npm (specifically the file @ esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.
- Warn about onResolve plugins not setting a path (#3790)
  
  Plugins that return values from onResolve without resolving the path (i.e. without setting either path or external: true) will now cause a warning. This is because esbuild only uses return values from onResolve if it successfully resolves the path, and it's not good for invalid input to be silently ignored.
- Add a new Go API for running the CLI with plugins (#3539)
  
  With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins) to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.
  
  This was contributed by @ edewit.
0.21.5 - 2024-06-09
Read more
0.21.4 - 2024-05-25
Read more
0.21.3 - 2024-05-15
Read more
0.21.2 - 2024-05-12
Read more
0.21.1 - 2024-05-07
Read more
0.21.0 - 2024-05-07
Read more
0.20.2 - 2024-03-14
0.20.1 - 2024-02-19
0.20.0 - 2024-01-27
0.19.12 - 2024-01-23
0.19.11 - 2023-12-29
0.19.10 - 2023-12-19
0.19.9 - 2023-12-10
0.19.8 - 2023-11-26
0.19.7 - 2023-11-21
0.19.6 - 2023-11-19
0.19.5 - 2023-10-17
0.19.4 - 2023-09-28
0.19.3 - 2023-09-14
0.19.2 - 2023-08-14
0.19.1 - 2023-08-11
0.19.0 - 2023-08-08
0.18.20 - 2023-08-08
0.18.19 - 2023-08-07
0.18.18 - 2023-08-05
0.18.17 - 2023-07-26
0.18.16 - 2023-07-23
0.18.15 - 2023-07-20
0.18.14 - 2023-07-18
0.18.13 - 2023-07-15
0.18.12 - 2023-07-13
0.18.11 - 2023-07-01
0.18.10 - 2023-06-26
0.18.9 - 2023-06-26
0.18.8 - 2023-06-25
0.18.7 - 2023-06-24
0.18.6 - 2023-06-20
0.18.5 - 2023-06-20
0.18.4 - 2023-06-16
0.18.3 - 2023-06-15
0.18.2 - 2023-06-13
0.18.1 - 2023-06-12
0.18.0 - 2023-06-09
0.17.19 - 2023-05-13
0.17.18 - 2023-04-22
0.17.17 - 2023-04-16
0.17.16 - 2023-04-10
0.17.15 - 2023-04-01
0.17.14 - 2023-03-26
0.17.13 - 2023-03-24
0.17.12 - 2023-03-17
0.17.11 - 2023-03-03
0.17.10 - 2023-02-20
0.17.9 - 2023-02-19
0.17.8 - 2023-02-13
0.17.7 - 2023-02-09
0.17.6 - 2023-02-06
0.17.5 - 2023-01-27
0.17.4 - 2023-01-22
0.17.3 - 2023-01-18
0.17.2 - 2023-01-17
0.17.1 - 2023-01-16
0.17.0 - 2023-01-14
0.16.17 - 2023-01-11
0.16.16 - 2023-01-08
0.16.15 - 2023-01-07
0.16.14 - 2023-01-04
0.16.13 - 2023-01-02
0.16.12 - 2022-12-28
0.16.11 - 2022-12-27
0.16.10 - 2022-12-19
0.16.9 - 2022-12-18
0.16.8 - 2022-12-16
0.16.7 - 2022-12-14
0.16.6 - 2022-12-14
0.16.5 - 2022-12-13
0.16.4 - 2022-12-10
0.16.3 - 2022-12-08
0.16.2 - 2022-12-08
0.16.1 - 2022-12-07
0.16.0 - 2022-12-07
0.15.18 - 2022-12-05

from esbuild GitHub release notes

Commit messages

Package name: esbuild

d34e79e publish 0.24.0 to npm
045a87f fix Introduce TraitRefs, remove cell_local vercel/turborepo#3887: omit dead export warning for `default`
6e049b8 fix feat(blog): 1.8 post (#3913 vercel/turborepo#3913: useDefineForClassFields and decorators
9c26f98 lower decorators for useDefineForClassFields feat(blog): 1.8 post (#3913 vercel/turborepo#3913
46fdb68 fix feature: Use error_for_status vercel/turborepo#3898: incorrect cyclic tsconfig.json warning
b500443 fix Customize Script Choosing vercel/turborepo#3917: running esbuild cli with deno
b125e62 run `make update-compat-table`
112b9aa fix release(turborepo): 1.8.2 vercel/turborepo#3915: stack overflow with yarn + tsconfig
ed5a555 wasm: catch and rethrow stack overflows (release(turborepo): 1.8.2 vercel/turborepo#3915)
11d3196 fix Error messaging when using nonexistent task name vercel/turborepo#3902: update go 1.22.5 => 1.23.1
2de2f74 run `make update-compat-table`
3327274 publish 0.23.1 to npm
38e22ed add a warning/debug log message for How to work with apps/ specific environment variables? vercel/turborepo#3867
a15bb51 fix docs: revert webpack loader documentation for now vercel/turborepo#3825: memory leak of `pluginData` values
f6e6481 fix no longer build arm64 go builds vercel/turborepo#3838: print comments before `case` clauses
9c13ae1 fix Use IndexSet in IntrospectableChildrenVc vercel/turborepo#3853: update go 1.22.4 => 1.22.5
78f89e4 fix fix: test.yml vercel/turborepo#3845: some incorrect error message locations
892d2a7 fix Move workspace-specific tasks to workspace configs vercel/turborepo#3834: cli sometimes panics with `--analyze`
360d472 fix a typo in the release notes
e3f4e2d fix feat(types): update turbo.json schema vercel/turborepo#3821: allow `node:` prefix with `es*` targets
9d50680 publish 0.23.0 to npm
ac7fd04 Revert "fix fix(deps): update module github.com/briandowns/spinner to v1.19.0 vercel/turborepo#1874: node defaults to `--packages=external`" (Ensure Task can depend across workspaces vercel/turborepo#3820)
626ac2c fix feat(@turbo/workspaces): add new workspaces package (#3818 vercel/turborepo#3818: preserve collapsed jsx whitespace
7c2eb2e hashbang syntax is part of es2023

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade esbuild from 0.15.18 to 0.24.0. See this package in npm: https://www.npmjs.com/package/esbuild See this project in Snyk: https://app.snyk.io/org/sammytezzy/project/1e70f5b6-c7c2-487f-819a-c1c9c946cb96?utm_source=github&utm_medium=referral&page=upgrade-pr

stackblitz · 2024-10-18T17:13:30Z

Run & review this pull request in StackBlitz Codeflow.

changeset-bot · 2024-10-18T17:13:30Z

⚠️ No Changeset found

Latest commit: 8ed4595

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

sourcery-ai

We have skipped reviewing this pull request. Here's why:

It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
We don't review packaging changes - Let us know if you'd like us to change this.

sourcery-ai bot reviewed Oct 18, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Snyk] Upgrade esbuild from 0.15.18 to 0.24.0 #335

[Snyk] Upgrade esbuild from 0.15.18 to 0.24.0 #335

X-oss-byte commented Oct 18, 2024

stackblitz bot commented Oct 18, 2024

changeset-bot bot commented Oct 18, 2024

sourcery-ai bot left a comment

[Snyk] Upgrade esbuild from 0.15.18 to 0.24.0 #335

Are you sure you want to change the base?

[Snyk] Upgrade esbuild from 0.15.18 to 0.24.0 #335

Conversation

X-oss-byte commented Oct 18, 2024

Snyk has created this PR to upgrade esbuild from 0.15.18 to 0.24.0.

stackblitz bot commented Oct 18, 2024

changeset-bot bot commented Oct 18, 2024

⚠️ No Changeset found

sourcery-ai bot left a comment

Choose a reason for hiding this comment