[Snyk] Upgrade esbuild from 0.17.19 to 0.18.0 #286

fraxken · 2023-07-01T00:37:02Z

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

Snyk has created this PR to upgrade esbuild from 0.17.19 to 0.18.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 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-06-09.

Release notes

Package name: esbuild

0.18.0 - 2023-06-09
Read more
0.17.19 - 2023-05-13
- Fix CSS transform bugs with nested selectors that start with a combinator (#3096)
  
  This release fixes several bugs regarding transforming nested CSS into non-nested CSS for older browsers. The bugs were due to lack of test coverage for nested selectors with more than one compound selector where they all start with the same combinator. Here's what some problematic cases look like before and after these fixes:
  
  / Original code */
  .foo {
  > &a,
  > &b {
  color: red;
  }
  }
  .bar {
  > &a,
  + &b {
  color: green;
  }
  }
  
  /* Old output (with --target=chrome90) */
  .foo :is(> .fooa, > .foob) {
  color: red;
  }
  .bar :is(> .bara, + .barb) {
  color: green;
  }
  
  /* New output (with --target=chrome90) */
  .foo > :is(a.foo, b.foo) {
  color: red;
  }
  .bar > a.bar,
  .bar + b.bar {
  color: green;
  }
- Fix bug with TypeScript parsing of instantiation expressions followed by = (#3111)
  
  This release fixes esbuild's TypeScript-to-JavaScript conversion code in the case where a potential instantiation expression is followed immediately by a = token (such that the trailing > becomes a >= token). Previously esbuild considered that to still be an instantiation expression, but the official TypeScript compiler considered it to be a >= operator instead. This release changes esbuild's interpretation to match TypeScript. This edge case currently appears to be problematic for other TypeScript-to-JavaScript converters as well:
  
  Original code TypeScript esbuild 0.17.18 esbuild 0.17.19 Sucrase Babel
  
  x<y>=a<b<c>>() x<y>=a(); x=a(); x<y>=a(); x=a() Invalid left-hand side in assignment expression
- Avoid removing unrecognized directives from the directive prologue when minifying (#3115)
  
  The directive prologue in JavaScript is a sequence of top-level string expressions that come before your code. The only directives that JavaScript engines currently recognize are use strict and sometimes use asm. However, the people behind React have made up their own directive for their own custom dialect of JavaScript. Previously esbuild only preserved the use strict directive when minifying, although you could still write React JavaScript with esbuild using something like --banner:js="'your directive here';". With this release, you can now put arbitrary directives in the entry point and esbuild will preserve them in its minified output:
  
  // Original code
  'use wtf'; console.log(123)
  
  // Old output (with --minify)
  console.log(123);
  
  // New output (with --minify)
  "use wtf";console.log(123);
  
  Note that this means esbuild will no longer remove certain stray top-level strings when minifying. This behavior is an intentional change because these stray top-level strings are actually part of the directive prologue, and could potentially have semantics assigned to them (as was the case with React).
- Improved minification of binary shift operators
  
  With this release, esbuild's minifier will now evaluate the << and >>> operators if the resulting code would be shorter:
  
  // Original code
  console.log(10 << 10, 10 << 20, -123 >>> 5, -123 >>> 10);
  
  // Old output (with --minify)
  console.log(10<<10,10<<20,-123>>>5,-123>>>10);
  
  // New output (with --minify)
  console.log(10240,10<<20,-123>>>5,4194303);

from esbuild GitHub release notes

Commit messages

Package name: esbuild

4dda49d publish 0.18.0 to npm
54ae996 prefer `.js` over `.ts` in `node_modules` (#3019)
b7426bd fix #2481: skip tsconfig paths inside node_modules
545964b update go 1.20.4 => 1.20.5
513e752 ts 5.0: multiple inheritance for `tsconfig.json`
ab7921d fix #2386: ignore `tsconfig.json` in all packages
8e56452 avoid tsconfig `extends` for the `transform` api
35d04d5 add test for `tsconfigRaw` and virtual files
4632160 fix chore: setup Node.js CI #385, fix #2543, fix #943, fix #2440: tsconfig
76fb8bc minify now unwraps inlined enum property keys
c6fdc7f add `--sourcemap` in repl demo links
e6a8169 release notes for #797
5e50349 patch bad useDefineForClassFields value in sucrase tests
8dc7a56 forbid `&` before a type selector in nested css
905959f fix #3119: avoid `:is()` with pseudo-elements
e7481cd fix #2634: ignore `"jsx": "preserve"` in tsconfig
6f2c029 require `"experimentalDecorators": true` (chore(deps-dev): bump eslint from 7.5.0 to 7.10.0 #104)
ead6b72 rename some tests
a4b792a fix: remove empty `export {} from` in typescript
414fc69 add support for `verbatimModuleSyntax`
664353a group tsconfig settings into a shared object
9be7875 fix #2628, fix #2584, fix #2993: `target` changes
a4e06b1 move jsx settings from "tsconfig.json" to object
dea503c parse the full value of "jsx" in "tsconfig.json"