[Snyk] Upgrade esbuild from 0.14.38 to 0.14.39 #255

ytetsuro · 2022-06-03T04:57:32Z

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade esbuild from 0.14.38 to 0.14.39.

ℹ️ 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 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2022-05-11.

Release notes

Package name: esbuild

0.14.39 - 2022-05-11
- Fix code generation for export default and /* @ __PURE__ */ call (#2203)
  
  The /* @ __PURE__ */ comment annotation can be added to function calls to indicate that they are side-effect free. These annotations are passed through into the output by esbuild since many JavaScript tools understand them. However, there was an edge case where printing this comment before a function call caused esbuild to fail to parenthesize a function literal because it thought it was no longer at the start of the expression. This problem has been fixed:
  
  // Original code
  export default / @ PURE */ (function() {
  })()
  
  // Old output
  export default /* @ PURE */ function() {
  }();
  
  // New output
  export default /* @ PURE */ (function() {
  })();
- Preserve ... before JSX child expressions (#2245)
  
  TypeScript 4.5 changed how JSX child expressions that start with ... are emitted. Previously the ... was omitted but starting with TypeScript 4.5, the ... is now preserved instead. This release updates esbuild to match TypeScript's new output in this case:
  
  // Original code
  console.log(<a>{...b}</a>)
  
  // Old output
  console.log(/* @ PURE */ React.createElement("a", null, b));
  
  // New output
  console.log(/* @ PURE */ React.createElement("a", null, ...b));
  
  Note that this behavior is TypeScript-specific. Babel doesn't support the ... token at all (it gives the error "Spread children are not supported in React").
- Slightly adjust esbuild's handling of the browser field in package.json (#2239)
  
  This release changes esbuild's interpretation of browser path remapping to fix a regression that was introduced in esbuild version 0.14.21. Browserify has a bug where it incorrectly matches package paths to relative paths in the browser field, and esbuild replicates this bug for compatibility with Browserify. I have a set of tests that I use to verify that esbuild's replication of this Browserify is accurate here: https://github.com/evanw/package-json-browser-tests. However, I was missing a test case and esbuild's behavior diverges from Browserify in this case. This release now handles this edge case as well:
  - entry.js:
```
require('pkg/sub')
```
  - node_modules/pkg/package.json:
```
{
  "browser": {
    "./sub": "./sub/foo.js",
    "./sub/sub.js": "./sub/foo.js"
  }
}
```
  - node_modules/pkg/sub/foo.js:
```
require('sub')
```
  - node_modules/sub/index.js:
```
console.log('works')
```
  The import path sub in require('sub') was previously matching the remapping "./sub/sub.js": "./sub/foo.js" but with this release it should now no longer match that remapping. Now require('sub') will only match the remapping "./sub/sub": "./sub/foo.js" (without the trailing .js). Browserify apparently only matches without the .js suffix here.

0.14.38 - 2022-04-21

Further fixes to TypeScript 4.7 instantiation expression parsing (#2201)

This release fixes some additional edge cases with parsing instantiation expressions from the upcoming version 4.7 of TypeScript. Previously it was allowed for an instantiation expression to precede a binary operator but with this release, that's no longer allowed. This was sometimes valid in the TypeScript 4.7 beta but is no longer allowed in the latest version of TypeScript 4.7. Fixing this also fixed a regression that was introduced by the previous release of esbuild:

Code	TS 4.6.3	TS 4.7.0 beta	TS 4.7.0 nightly	esbuild 0.14.36	esbuild 0.14.37	esbuild 0.14.38
`a<b> == c<d>`	Invalid	`a == c`	Invalid	`a == c`	`a == c`	Invalid
`a<b> in c<d>`	Invalid	Invalid	Invalid	Invalid	`a in c`	Invalid
`a<b>>=c<d>`	Invalid	Invalid	Invalid	Invalid	`a >= c`	Invalid
`a<b>=c<d>`	Invalid	`a < b >= c`	`a = c`	`a < b >= c`	`a = c`	`a = c`
`a<b>>c<d>`	`a < b >> c`	`a < b >> c`	`a < b >> c`	`a < b >> c`	`a > c`	`a < b >> c`

This table illustrates some of the more significant changes between all of these parsers. The most important part is that esbuild 0.14.38 now matches the behavior of the latest TypeScript compiler for all of these cases.

from esbuild GitHub release notes

Commit messages

Package name: esbuild