chore(deps): update dependency esbuild to ~0.14.0

Open renovate[bot] opened this issue 4 years ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	`~0.12.29` -> `~0.14.0`

Release Notes

evanw/esbuild

`v0.14.54`

Compare Source

Fix optimizations for calls containing spread arguments (#2445)

This release fixes the handling of spread arguments in the optimization of /* @__PURE__ */ comments, empty functions, and identity functions:
```
// Original code
function empty() {}
function identity(x) { return x }
/* @&#8203;__PURE__ */ a(...x)
/* @&#8203;__PURE__ */ new b(...x)
empty(...x)
identity(...x)

// Old output (with --minify --tree-shaking=true)
...x;...x;...x;...x;

// New output (with --minify --tree-shaking=true)
function identity(n){return n}[...x];[...x];[...x];identity(...x);
```
Previously esbuild assumed arguments with side effects could be directly inlined. This is almost always true except for spread arguments, which are not syntactically valid on their own and which have the side effect of causing iteration, which might have further side effects. Now esbuild will wrap these elements in an unused array so that they are syntactically valid and so that the iteration side effects are preserved.

This release fixes a minor issue with the previous release: I had to rename the package esbuild-linux-loong64 to @esbuild/linux-loong64 in the contributed PR because someone registered the package name before I could claim it, and I missed a spot. Hopefully everything is working after this release. I plan to change all platform-specific package names to use the @esbuild/ scope at some point to avoid this problem in the future.

`v0.14.52`

Compare Source

Allow binary data as input to the JS transform and build APIs (#2424)

Previously esbuild's transform and build APIs could only take a string. However, some people want to use esbuild to convert binary data to base64 text. This is problematic because JavaScript strings represent UTF-16 text and esbuild internally operates on arrays of bytes, so all strings coming from JavaScript undergo UTF-16 to UTF-8 conversion before use. This meant that using esbuild in this way was doing base64 encoding of the UTF-8 encoding of the text, which was undesired.

With this release, esbuild now accepts Uint8Array in addition to string as an input format for the transform and build APIs. Now you can use esbuild to convert binary data to base64 text:

// Original code
import esbuild from 'esbuild'
console.log([
  (await esbuild.transform('\xFF', { loader: 'base64' })).code,
  (await esbuild.build({ stdin: { contents: '\xFF', loader: 'base64' }, write: false })).outputFiles[0].text,
])
console.log([
  (await esbuild.transform(new Uint8Array([0xFF]), { loader: 'base64' })).code,
  (await esbuild.build({ stdin: { contents: new Uint8Array([0xFF]), loader: 'base64' }, write: false })).outputFiles[0].text,
])

// Old output
[ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
/* ERROR: The input to "transform" must be a string */

// New output
[ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
[ 'module.exports = "/w==";\n', 'module.exports = "/w==";\n' ]

Update the getter for text in build results (#2423)

Output files in build results returned from esbuild's JavaScript API have both a contents and a text property to return the contents of the output file. The contents property is a binary UTF-8 Uint8Array and the text property is a JavaScript UTF-16 string. The text property is a getter that does the UTF-8 to UTF-16 conversion only if it's needed for better performance.

Previously if you mutate the build results object, you had to overwrite both contents and text since the value returned from the text getter is the original text returned by esbuild. Some people find this confusing so with this release, the getter for text has been updated to do the UTF-8 to UTF-16 conversion on the current value of the contents property instead of the original value.
Publish builds for Linux LoongArch 64-bit (#1804, #2373)

This release upgrades to Go 1.19, which now includes support for LoongArch 64-bit processors. LoongArch 64-bit builds of esbuild will now be published to npm, which means that in theory they can now be installed with npm install esbuild. This was contributed by @beyond-1234.

`v0.14.51`

Compare Source

Add support for React 17's automatic JSX transform (#334, #718, #1172, #2318, #2349)

This adds support for the new "automatic" JSX runtime from React 17+ to esbuild for both the build and transform APIs.

New CLI flags and API options:
- --jsx, jsx — Set this to "automatic" to opt in to this new transform
- --jsx-dev, jsxDev — Toggles development mode for the automatic runtime
- --jsx-import-source, jsxImportSource — Overrides the root import for runtime functions (default "react")
New JSX pragma comments:
- @jsxRuntime — Sets the runtime (automatic or classic)
- @jsxImportSource — Sets the import source (only valid with automatic runtime)
The existing @jsxFragment and @jsxFactory pragma comments are only valid with "classic" runtime.

TSConfig resolving: Along with accepting the new options directly via CLI or API, option inference from tsconfig.json compiler options was also implemented:
- "jsx": "preserve" or "jsx": "react-native" → Same as --jsx=preserve in esbuild
- "jsx": "react" → Same as --jsx=transform in esbuild (which is the default behavior)
- "jsx": "react-jsx" → Same as --jsx=automatic in esbuild
- "jsx": "react-jsxdev" → Same as --jsx=automatic --jsx-dev in esbuild
It also reads the value of "jsxImportSource" from tsconfig.json if specified.

For react-jsx it's important to note that it doesn't implicitly disable --jsx-dev. This is to support the case where a user sets "react-jsx" in their tsconfig.json but then toggles development mode directly in esbuild.

esbuild vs Babel vs TS vs...

There are a few differences between the various technologies that implement automatic JSX runtimes. The JSX transform in esbuild follows a mix of Babel's and TypeScript's behavior:
- When an element has __source or __self props:
  - Babel: Print an error about a deprecated transform plugin
  - TypeScript: Allow the props
  - swc: Hard crash
  - esbuild: Print an error — Following Babel was chosen for this one because this might help people catch configuration issues where JSX files are being parsed by multiple tools
- Element has an "implicit true" key prop, e.g. <a key />:
  - Babel: Print an error indicating that "key" props require an explicit value
  - TypeScript: Silently omit the "key" prop
  - swc: Hard crash
  - esbuild: Print an error like Babel — This might help catch legitimate programming mistakes
- Element has spread children, e.g. <a>{...children}</a>
  - Babel: Print an error stating that React doesn't support spread children
  - TypeScript: Use static jsx function and pass children as-is, including spread operator
  - swc: same as Babel
  - esbuild: Same as TypeScript
Also note that TypeScript has some bugs regarding JSX development mode and the generation of lineNumber and columnNumber values. Babel's values are accurate though, so esbuild's line and column numbers match Babel. Both numbers are 1-based and columns are counted in terms of UTF-16 code units.

This feature was contributed by @jgoz.

`v0.14.50`

Compare Source

Emit names in source maps (#1296)

The source map specification includes an optional names field that can associate an identifier with a mapping entry. This can be used to record the original name for an identifier, which is useful if the identifier was renamed to something else in the generated code. When esbuild was originally written, this field wasn't widely used, but now there are some debuggers that make use of it to provide better debugging of minified code. With this release, esbuild now includes a names field in the source maps that it generates. To save space, the original name is only recorded when it's different from the final name.
Update parser for arrow functions with initial default type parameters in .tsx files (#2410)

TypeScript 4.6 introduced a change to the parsing of JSX syntax in .tsx files. Now a < token followed by an identifier and then a = token is parsed as an arrow function with a default type parameter instead of as a JSX element. This release updates esbuild's parser to match TypeScript's parser.
Fix an accidental infinite loop with --define substitution (#2407)

This is a fix for a regression that was introduced in esbuild version 0.14.44 where certain --define substitutions could result in esbuild crashing with a stack overflow. The problem was an incorrect fix for #2292. The fix merged the code paths for --define and --jsx-factory rewriting since the value substitution is now the same for both. However, doing this accidentally made --define substitution recursive since the JSX factory needs to be able to match against --define substitutions to integrate with the --inject feature. The fix is to only do one additional level of matching against define substitutions, and to only do this for JSX factories. Now these cases are able to build successfully without a stack overflow.
Include the "public path" value in hashes (#2403)

The --public-path= configuration value affects the paths that esbuild uses to reference files from other files and is used in various situations such as cross-chunk imports in JS and references to asset files from CSS files. However, it wasn't included in the hash calculations used for file names due to an oversight. This meant that changing the public path setting incorrectly didn't result in the hashes in file names changing even though the contents of the files changed. This release fixes the issue by including a hash of the public path in all non-asset output files.
Fix a cross-platform consistency bug (#2383)

Previously esbuild would minify 0xFFFF_FFFF_FFFF_FFFF as 0xffffffffffffffff (18 bytes) on arm64 chips and as 18446744073709552e3 (19 bytes) on x86_64 chips. The reason was that the number was converted to a 64-bit unsigned integer internally for printing as hexadecimal, the 64-bit floating-point number 0xFFFF_FFFF_FFFF_FFFF is actually 0x1_0000_0000_0000_0180 (i.e. it's rounded up, not down), and converting float64 to uint64 is implementation-dependent in Go when the input is out of bounds. This was fixed by changing the upper limit for which esbuild uses hexadecimal numbers during minification to 0xFFFF_FFFF_FFFF_F800, which is the next representable 64-bit floating-point number below 0x1_0000_0000_0000_0180, and which fits in a uint64. As a result, esbuild will now consistently never minify 0xFFFF_FFFF_FFFF_FFFF as 0xffffffffffffffff anymore, which means the output should now be consistent across platforms.
Fix a hang with the synchronous API when the package is corrupted (#2396)

An error message is already thrown when the esbuild package is corrupted and esbuild can't be run. However, if you are using a synchronous call in the JavaScript API in worker mode, esbuild will use a child worker to initialize esbuild once so that the overhead of initializing esbuild can be amortized across multiple synchronous API calls. However, errors thrown during initialization weren't being propagated correctly which resulted in a hang while the main thread waited forever for the child worker to finish initializing. With this release, initialization errors are now propagated correctly so calling a synchronous API call when the package is corrupted should now result in an error instead of a hang.
Fix tsconfig.json files that collide with directory names (#2411)

TypeScript lets you write tsconfig.json files with extends clauses that refer to another config file using an implicit .json file extension. However, if the config file without the .json extension existed as a directory name, esbuild and TypeScript had different behavior. TypeScript ignores the directory and continues looking for the config file by adding the .json extension while esbuild previously terminated the search and then failed to load the config file (because it's a directory). With this release, esbuild will now ignore exact matches when resolving extends fields in tsconfig.json files if the exact match results in a directory.
Add platform to the transform API (#2362)

The platform option is mainly relevant for bundling because it mostly affects path resolution (e.g. activating the "browser" field in package.json files), so it was previously only available for the build API. With this release, it has additionally be made available for the transform API for a single reason: you can now set --platform=node when transforming a string so that esbuild will add export annotations for node, which is only relevant when --format=cjs is also present.

This has to do with an implementation detail of node that parses the AST of CommonJS files to discover named exports when importing CommonJS from ESM. However, this new addition to esbuild's API is of questionable usefulness. Node's loader API (the main use case for using esbuild's transform API like this) actually bypasses the content returned from the loader and parses the AST that's present on the file system, so you won't actually be able to use esbuild's API for this. See the linked issue for more information.

`v0.14.49`

Compare Source

Keep inlined constants when direct eval is present (#2361)

Version 0.14.19 of esbuild added inlining of certain const variables during minification, which replaces all references to the variable with the initializer and then removes the variable declaration. However, this could generate incorrect code when direct eval is present because the direct eval could reference the constant by name. This release fixes the problem by preserving the const variable declaration in this case:
```
// Original code
console.log((() => { const x = 123; return x + eval('x') }))

// Old output (with --minify)
console.log(()=>123+eval("x"));

// New output (with --minify)
console.log(()=>{const x=123;return 123+eval("x")});
```
Fix an incorrect error in TypeScript when targeting ES5 (#2375)

Previously when compiling TypeScript code to ES5, esbuild could incorrectly consider the following syntax forms as a transformation error:
```
0 ? ([]) : 1 ? ({}) : 2;
```
The error messages looked like this:
```
✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet

    example.ts:1:5:
      1 │ 0 ? ([]) : 1 ? ({}) : 2;
        ╵      ^

✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet

    example.ts:1:16:
      1 │ 0 ? ([]) : 1 ? ({}) : 2;
        ╵                 ^
```
These parenthesized literals followed by a colon look like the start of an arrow function expression followed by a TypeScript return type (e.g. ([]) : 1 could be the start of the TypeScript arrow function ([]): 1 => 1). Unlike in JavaScript, parsing arrow functions in TypeScript requires backtracking. In this case esbuild correctly determined that this expression wasn't an arrow function after all but the check for destructuring was incorrectly not covered under the backtracking process. With this release, the error message is now only reported if the parser successfully parses an arrow function without backtracking.
Fix generated TypeScript enum comments containing */ (#2369, #2371)

TypeScript enum values that are equal to a number or string literal are inlined (references to the enum are replaced with the literal value) and have a /* ... */ comment after them with the original enum name to improve readability. However, this comment is omitted if the enum name contains the character sequence */ because that would end the comment early and cause a syntax error:
```
// Original TypeScript
enum Foo { '/*' = 1, '*/' = 2 }
console.log(Foo['/*'], Foo['*/'])

// Generated JavaScript
console.log(1 /* /* */, 2);
```
This was originally handled correctly when TypeScript enum inlining was initially implemented since it was only supported within a single file. However, when esbuild was later extended to support TypeScript enum inlining across files, this special case where the enum name contains */ was not handled in that new code. Starting with this release, esbuild will now handle enums with names containing */ correctly when they are inlined across files:
```
// foo.ts
export enum Foo { '/*' = 1, '*/' = 2 }

// bar.ts
import { Foo } from './foo'
console.log(Foo['/*'], Foo['*/'])

// Old output (with --bundle --format=esm)
console.log(1 /* /* */, 2 /* */ */);

// New output (with --bundle --format=esm)
console.log(1 /* /* */, 2);
```
This fix was contributed by @magic-akari.
Allow declare class fields to be initialized (#2380)

This release fixes an oversight in the TypeScript parser that disallowed initializers for declare class fields. TypeScript actually allows the following limited initializer expressions for readonly fields:
```
declare const enum a { b = 0 }

class Foo {
  // These are allowed by TypeScript
  declare readonly a = 0
  declare readonly b = -0
  declare readonly c = 0n
  declare readonly d = -0n
  declare readonly e = 'x'
  declare readonly f = `x`
  declare readonly g = a.b
  declare readonly h = a['b']

  // These are not allowed by TypeScript
  declare readonly x = (0)
  declare readonly y = null
  declare readonly z = -a.b
}
```
So with this release, esbuild now allows initializers for declare class fields too. To future-proof this in case TypeScript allows more expressions as initializers in the future (such as null), esbuild will allow any expression as an initializer and will leave the specifics of TypeScript's special-casing here to the TypeScript type checker.
Fix a bug in esbuild's feature compatibility table generator (#2365)

Passing specific JavaScript engines to esbuild's --target flag restricts esbuild to only using JavaScript features that are supported on those engines in the output files that esbuild generates. The data for this feature is automatically derived from this compatibility table with a script: https://kangax.github.io/compat-table/.

However, the script had a bug that could incorrectly consider a JavaScript syntax feature to be supported in a given engine even when it doesn't actually work in that engine. Specifically this bug happened when a certain aspect of JavaScript syntax has always worked incorrectly in that engine and the bug in that engine has never been fixed. This situation hasn't really come up before because previously esbuild pretty much only targeted JavaScript engines that always fix their bugs, but the two new JavaScript engines that were added in the previous release (Hermes and Rhino) have many aspects of the JavaScript specification that have never been implemented, and may never be implemented. For example, the let and const keywords are not implemented correctly in those engines.

With this release, esbuild's compatibility table generator script has been fixed and as a result, esbuild will now correctly consider a JavaScript syntax feature to be unsupported in a given engine if there is some aspect of that syntax that is broken in all known versions of that engine. This means that the following JavaScript syntax features are no longer considered to be supported by these engines (represented using esbuild's internal names for these syntax features):

Hermes:
- arrow
- const-and-let
- default-argument
- generator
- optional-catch-binding
- optional-chain
- rest-argument
- template-literal
Rhino:
- arrow
- const-and-let
- destructuring
- for-of
- generator
- object-extensions
- template-literal
IE:
- const-and-let

`v0.14.48`

Compare Source

Enable using esbuild in Deno via WebAssembly (#2323)

The native implementation of esbuild is much faster than the WebAssembly version, but some people don't want to give Deno the --allow-run permission necessary to run esbuild and are ok waiting longer for their builds to finish when using the WebAssembly backend. With this release, you can now use esbuild via WebAssembly in Deno. To do this you will need to import from wasm.js instead of mod.js:
```
import * as esbuild from 'https://deno.land/x/[email protected]/wasm.js'
const ts = 'let test: boolean = true'
const result = await esbuild.transform(ts, { loader: 'ts' })
console.log('result:', result)
```
Make sure you run Deno with --allow-net so esbuild can download the WebAssembly module. Using esbuild like this starts up a worker thread that runs esbuild in parallel (unless you call esbuild.initialize({ worker: false }) to tell esbuild to run on the main thread). If you want to, you can call esbuild.stop() to terminate the worker if you won't be using esbuild anymore and you want to reclaim the memory.

Note that Deno appears to have a bug where background WebAssembly optimization can prevent the process from exiting for many seconds. If you are trying to use Deno and WebAssembly to run esbuild quickly, you may need to manually call Deno.exit(0) after your code has finished running.
Add support for font file MIME types (#2337)

This release adds support for font file MIME types to esbuild, which means they are now recognized by the built-in local web server and they are now used when a font file is loaded using the dataurl loader. The full set of newly-added file extension MIME type mappings is as follows:
- .eot => application/vnd.ms-fontobject
- .otf => font/otf
- .sfnt => font/sfnt
- .ttf => font/ttf
- .woff => font/woff
- .woff2 => font/woff2
Remove "use strict"; when targeting ESM (#2347)

All ES module code is automatically in strict mode, so a "use strict"; directive is unnecessary. With this release, esbuild will now remove the "use strict"; directive if the output format is ESM. This change makes the generated output file a few bytes smaller:
```
// Original code
'use strict'
export let foo = 123

// Old output (with --format=esm --minify)
"use strict";let t=123;export{t as foo};

// New output (with --format=esm --minify)
let t=123;export{t as foo};
```
Attempt to have esbuild work with Deno on FreeBSD (#2356)

Deno doesn't support FreeBSD, but it's possible to build Deno for FreeBSD with some additional patches on top. This release of esbuild changes esbuild's Deno installer to download esbuild's FreeBSD binary in this situation. This configuration is unsupported although in theory everything should work.
Add some more target JavaScript engines (#2357)

This release adds the Rhino and Hermes JavaScript engines to the set of engine identifiers that can be passed to the --target flag. You can use this to restrict esbuild to only using JavaScript features that are supported on those engines in the output files that esbuild generates.

`v0.14.47`

Compare Source

Make global names more compact when ||= is available (#2331)

With this release, the code esbuild generates for the --global-name= setting is now slightly shorter when you don't configure esbuild such that the ||= operator is unsupported (e.g. with --target=chrome80 or --supported:logical-assignment=false):

// Original code
exports.foo = 123

// Old output (with --format=iife --global-name=foo.bar.baz --minify)
var foo=foo||{};foo.bar=foo.bar||{};foo.bar.baz=(()=>{var b=(a,o)=>()=>(o||a((o={exports:{}}).exports,o),o.exports);var c=b(f=>{f.foo=123});return c();})();

// New output (with --format=iife --global-name=foo.bar.baz --minify)
var foo;((foo||={}).bar||={}).baz=(()=>{var b=(a,o)=>()=>(o||a((o={exports:{}}).exports,o),o.exports);var c=b(f=>{f.foo=123});return c();})();

Fix --mangle-quoted=false with --minify-syntax=true

If property mangling is active and --mangle-quoted is disabled, quoted properties are supposed to be preserved. However, there was a case when this didn't happen if --minify-syntax was enabled, since that internally transforms x['y'] into x.y to reduce code size. This issue has been fixed:
```
// Original code
x.foo = x['bar'] = { foo: y, 'bar': z }

// Old output (with --mangle-props=. --mangle-quoted=false --minify-syntax=true)
x.a = x.b = { a: y, bar: z };

// New output (with --mangle-props=. --mangle-quoted=false --minify-syntax=true)
x.a = x.bar = { a: y, bar: z };
```
Notice how the property foo is always used unquoted but the property bar is always used quoted, so foo should be consistently mangled while bar should be consistently not mangled.
Fix a minification bug regarding this and property initializers

When minification is enabled, esbuild attempts to inline the initializers of variables that have only been used once into the start of the following expression to reduce code size. However, there was a bug where this transformation could change the value of this when the initializer is a property access and the start of the following expression is a call expression. This release fixes the bug:
```
// Original code
function foo(obj) {
  let fn = obj.prop;
  fn();
}

// Old output (with --minify)
function foo(f){f.prop()}

// New output (with --minify)
function foo(o){let f=o.prop;f()}
```

`v0.14.46`

Compare Source

Add the ability to override support for individual syntax features (#2060, #2290, #2308)

The target setting already lets you configure esbuild to restrict its output by only making use of syntax features that are known to be supported in the configured target environment. For example, setting target to chrome50 causes esbuild to automatically transform optional chain expressions into the equivalent older JavaScript and prevents you from using BigInts, among many other things. However, sometimes you may want to customize this set of unsupported syntax features at the individual feature level.

Some examples of why you might want to do this:
- JavaScript runtimes often do a quick implementation of newer syntax features that is slower than the equivalent older JavaScript, and you can get a speedup by telling esbuild to pretend this syntax feature isn't supported. For example, V8 has a long-standing performance bug regarding object spread that can be avoided by manually copying properties instead of using object spread syntax. Right now esbuild hard-codes this optimization if you set target to a V8-based runtime.
- There are many less-used JavaScript runtimes in addition to the ones present in browsers, and these runtimes sometimes just decide not to implement parts of the specification, which might make sense for runtimes intended for embedded environments. For example, the developers behind Facebook's JavaScript runtime Hermes have decided to not implement classes despite it being a major JavaScript feature that was added seven years ago and that is used in virtually every large JavaScript project.
- You may be processing esbuild's output with another tool, and you may want esbuild to transform certain features and the other tool to transform certain other features. For example, if you are using esbuild to transform files individually to ES5 but you are then feeding the output into Webpack for bundling, you may want to preserve import() expressions even though they are a syntax error in ES5.
With this release, you can now use --supported:feature=false to force feature to be unsupported. This will cause esbuild to either rewrite code that uses the feature into older code that doesn't use the feature (if esbuild is able to), or to emit a build error (if esbuild is unable to). For example, you can use --supported:arrow=false to turn arrow functions into function expressions and --supported:bigint=false to make it an error to use a BigInt literal. You can also use --supported:feature=true to force it to be supported, which means esbuild will pass it through without transforming it. Keep in mind that this is an advanced feature. For most use cases you will probably want to just use target instead of using this.

The full set of currently-allowed features are as follows:

JavaScript:
- arbitrary-module-namespace-names
- array-spread
- arrow
- async-await
- async-generator
- bigint
- class
- class-field
- class-private-accessor
- class-private-brand-check
- class-private-field
- class-private-method
- class-private-static-accessor
- class-private-static-field
- class-private-static-method
- class-static-blocks
- class-static-field
- const-and-let
- default-argument
- destructuring
- dynamic-import
- exponent-operator
- export-star-as
- for-await
- for-of
- generator
- hashbang
- import-assertions
- import-meta
- logical-assignment
- nested-rest-binding
- new-target
- node-colon-prefix-import
- node-colon-prefix-require
- nullish-coalescing
- object-accessors
- object-extensions
- object-rest-spread
- optional-catch-binding
- optional-chain
- regexp-dot-all-flag
- regexp-lookbehind-assertions
- regexp-match-indices
- regexp-named-capture-groups
- regexp-sticky-and-unicode-flags
- regexp-unicode-property-escapes
- rest-argument
- template-literal
- top-level-await
- typeof-exotic-object-is-object
- unicode-escapes
CSS:
- hex-rgba
- rebecca-purple
- modern-rgb-hsl
- inset-property
- nesting
Since you can now specify --supported:object-rest-spread=false yourself to work around the V8 performance issue mentioned above, esbuild will no longer automatically transform all instances of object spread when targeting a V8-based JavaScript runtime going forward.

Note that JavaScript feature transformation is very complex and allowing full customization of the set of supported syntax features could cause bugs in esbuild due to new interactions between multiple features that were never possible before. Consider this to be an experimental feature.
Implement extends constraints on infer type variables (#2330)

TypeScript 4.7 introduced the ability to write an extends constraint after an infer type variable, which looks like this:
```
type FirstIfString<T> =
  T extends [infer S extends string, ...unknown[]]
    ? S
    : never;
```
You can read the blog post for more details: https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#extends-constraints-on-infer-type-variables. Previously this was a syntax error in esbuild but with this release, esbuild can now parse this syntax correctly.
Allow define to match optional chain expressions (#2324)

Previously esbuild's define feature only matched member expressions that did not use optional chaining. With this release, esbuild will now also match those that use optional chaining:
```
// Original code
console.log(a.b, a?.b)

// Old output (with --define:a.b=c)
console.log(c, a?.b);

// New output (with --define:a.b=c)
console.log(c, c);
```
This is for compatibility with Webpack's DefinePlugin, which behaves the same way.

`v0.14.45`

Compare Source

Add a log message for ambiguous re-exports (#2322)

In JavaScript, you can re-export symbols from another file using export * from './another-file'. When you do this from multiple files that export different symbols with the same name, this creates an ambiguous export which is causes that name to not be exported. This is harmless if you don't plan on using the ambiguous export name, so esbuild doesn't have a warning for this. But if you do want a warning for this (or if you want to make it an error), you can now opt-in to seeing this log message with --log-override:ambiguous-reexport=warning or --log-override:ambiguous-reexport=error. The log message looks like this:
```
▲ [WARNING] Re-export of "common" in "example.js" is ambiguous and has been removed [ambiguous-reexport]

  One definition of "common" comes from "a.js" here:

    a.js:2:11:
      2 │ export let common = 2
        ╵            ~~~~~~

  Another definition of "common" comes from "b.js" here:

    b.js:3:14:
      3 │ export { b as common }
        ╵               ~~~~~~
```
Optimize the output of the JSON loader (#2161)

The json loader (which is enabled by default for .json files) parses the file as JSON and generates a JavaScript file with the parsed expression as the default export. This behavior is standard and works in both node and the browser (well, as long as you use an import assertion). As an extension, esbuild also allows you to import additional top-level properties of the JSON object directly as a named export. This is beneficial for tree shaking. For example:
```
import { version } from 'esbuild/package.json'
console.log(version)
```
If you bundle the above code with esbuild, you'll get something like the following:
```
// node_modules/esbuild/package.json
var version = "0.14.44";

// example.js
console.log(version);
```
Most of the package.json file is irrelevant and has been omitted from the output due to tree shaking. The way esbuild implements this is to have the JavaScript file that's generated from the JSON look something like this with a separate exported variable for each property on the top-level object:
```
// node_modules/esbuild/package.json
export var name = "esbuild";
export var version = "0.14.44";
export var repository = "https://github.com/evanw/esbuild";
export var bin = {
  esbuild: "bin/esbuild"
};
...
export default {
  name,
  version,
  repository,
  bin,
  ...
};
```
However, this means that if you import the default export instead of a named export, you will get non-optimal output. The default export references all top-level properties, leading to many unnecessary variables in the output. With this release esbuild will now optimize this case to only generate additional variables for top-level object properties that are actually imported:
```
// Original code
import all, { bar } from 'data:application/json,{"foo":[1,2,3],"bar":[4,5,6]}'
console.log(all, bar)

// Old output (with --bundle --minify --format=esm)
var a=[1,2,3],l=[4,5,6],r={foo:a,bar:l};console.log(r,l);

// New output (with --bundle --minify --format=esm)
var l=[4,5,6],r={foo:[1,2,3],bar:l};console.log(r,l);
```
Notice how there is no longer an unnecessary generated variable for foo since it's never imported. And if you only import the default export, esbuild will now reproduce the original JSON object in the output with all top-level properties compactly inline.
Add id to warnings returned from the API

With this release, warnings returned from esbuild's API now have an id property. This identifies which kind of log message it is, which can be used to more easily filter out certain warnings. For example, reassigning a const variable will generate a message with an id of "assign-to-constant". This also gives you the identifier you need to apply a log override for that kind of message: https://esbuild.github.io/api/#log-override.

`v0.14.44`

Compare Source

Add a copy loader (#2255)

You can configure the "loader" for a specific file extension in esbuild, which is a way of telling esbuild how it should treat that file. For example, the text loader means the file is imported as a string while the binary loader means the file is imported as a Uint8Array. If you want the imported file to stay a separate file, the only option was previously the file loader (which is intended to be similar to Webpack's file-loader package). This loader copies the file to the output directory and imports the path to that output file as a string. This is useful for a web application because you can refer to resources such as .png images by importing them for their URL. However, it's not helpful if you need the imported file to stay a separate file but to still behave the way it normally would when the code is run without bundling.

With this release, there is now a new loader called copy that copies the loaded file to the output directory and then rewrites the path of the import statement or require() call to point to the copied file instead of the original file. This will automatically add a content hash to the output name by default (which can be configured with the --asset-names= setting). You can use this by specifying copy for a specific file extension, such as with --loader:.png=copy.
Fix a regression in arrow function lowering (#2302)

This release fixes a regression with lowering arrow functions to function expressions in ES5. This feature was introduced in version 0.7.2 and regressed in version 0.14.30.

In JavaScript, regular function expressions treat this as an implicit argument that is determined by how the function is called, but arrow functions treat this as a variable that is captured in the closure from the surrounding lexical scope. This is emulated in esbuild by storing the value of this in a variable before changing the arrow function into a function expression.

However, the code that did this didn't treat this expressions as a usage of that generated variable. Version 0.14.30 began omitting unused generated variables, which caused the transformation of this to break. This regression happened due to missing test coverage. With this release, the problem has been fixed:
```
// Original code
function foo() {
  return () => this
}

// Old output (with --target=es5)
function foo() {
  return function() {
    return _this;
  };
}

// New output (with --target=es5)
function foo() {
  var _this = this;
  return function() {
    return _this;
  };
}
```
This fix was contributed by @nkeynes.
Allow entity names as define values (#2292)

The "define" feature allows you to replace certain expressions with certain other expressions at compile time. For example, you might want to replace the global identifier IS_PRODUCTION with the boolean value true when building for production. Previously the only expressions you could substitute in were either identifier expressions or anything that is valid JSON syntax. This limitation exists because supporting more complex expressions is more complex (for example, substituting in a require() call could potentially pull in additional files, which would need to be handled). With this release, you can now also now define something as a member expression chain of the form foo.abc.xyz.
Implement package self-references (#2312)

This release implements a rarely-used feature in node where a package can import itself by name instead of using relative imports. You can read more about this feature here: https://nodejs.org/api/packages.html#self-referencing-a-package-using-its-name. For example, assuming the package.json in a given package looks like this:
```
// package.json
{
  "name": "a-package",
  "exports": {
    ".": "./main.mjs",
    "./foo": "./foo.js"
  }
}
```
Then any module in that package can reference an export in the package itself:
```
// ./a-module.mjs
import { something } from 'a-package'; // Imports "something" from ./main.mjs.
```
Self-referencing is also available when using require, both in an ES module, and in a CommonJS one. For example, this code will also work:
```
// ./a-module.js
const { something } = require('a-package/foo'); // Loads from ./foo.js.
```
Add a warning for assigning to an import (#2319)

Import bindings are immutable in JavaScript, and assigning to them will throw an error. So instead of doing this:
```
import { foo } from 'foo'
foo++
```
You need to do something like this instead:
```
import { foo, setFoo } from 'foo'
setFoo(foo + 1)
```
This is already an error if you try to bundle this code with esbuild. However, this was previously allowed silently when bundling is disabled, which can lead to confusion for people who don't know about this aspect of how JavaScript works. So with this release, there is now a warning when you do this:
```
▲ [WARNING] This assignment will throw because "foo" is an import [assign-to-import]

    example.js:2:0:
      2 │ foo++
        ╵ ~~~

  Imports are immutable in JavaScript. To modify the value of this import, you must export a setter
  function in the imported file (e.g. "setFoo") and then import and call that function here instead.
```
This new warning can be turned off with --log-override:assign-to-import=silent if you don't want to see it.
Implement alwaysStrict in tsconfig.json (#2264)

This release adds alwaysStrict to the set of TypeScript tsconfig.json configuration values that esbuild supports. When this is enabled, esbuild will forbid syntax that isn't allowed in strict mode and will automatically insert "use strict"; at the top of generated output files. This matches the behavior of the TypeScript compiler: https://www.typescriptlang.org/tsconfig#alwaysStrict.

`v0.14.43`

Compare Source

Fix TypeScript parse error whe a generic function is the first type argument (#2306)

In TypeScript, the << token may need to be split apart into two < tokens if it's present in a type argument context. This was already correctly handled for all type expressions and for identifier expressions such as in the following code:
```
// These cases already worked in the previous release
let foo: Array<<T>() => T>;
bar<<T>() => T>;
```
However, normal expressions of the following form were previously incorrectly treated as syntax errors:
```
// These cases were broken but have now been fixed
foo.bar<<T>() => T>;
foo?.<<T>() => T>();
```
With this release, these cases now parsed correctly.
Fix minification regression with pure IIFEs (#2279)

An Immediately Invoked Function Expression (IIFE) is a function call to an anonymous function, and is a way of introducing a new function-level scope in JavaScript since JavaScript lacks a way to do this otherwise. And a pure function call is a function call with the special /* @__PURE__ */ comment before it, which tells JavaScript build tools that the function call can be considered to have no side effects (and can be removed if it's unused).

Version 0.14.9 of esbuild introduced a regression that changed esbuild's behavior when these two features were combined. If the IIFE body contains a single expression, the resulting output still contained that expression instead of being empty. This is a minor regression because you normally wouldn't write code like this, so this shouldn't come up in practice, and it doesn't cause any correctness issues (just larger-than-necessary output). It's unusual that you would tell esbuild "remove this if the result is unused" and then not store the result anywhere, since the result is unused by construction. But regardless, the issue has now been fixed.

For example, the following code is a pure IIFE, which means it should be completely removed when minification is enabled. Previously it was replaced by the contents of the IIFE but it's now completely removed:
```
// Original code
/* @&#8203;__PURE__ */ (() => console.log(1))()

// Old output (with --minify)
console.log(1);

// New output (with --minify)
```
Add log messages for indirect require references (#2231)

A long time ago esbuild used to warn about indirect uses of require because they break esbuild's ability to analyze the dependencies of the code and cause dependencies to not be bundled, resulting in a potentially broken bundle. However, this warning was removed because many people wanted the warning to be removed. Some packages have code that uses require like this but on a code path that isn't used at run-time, so their code still happens to work even though the bundle is incomplete. For example, the following code will not bundle bindings:
```
// Prevent React Native packager from seeing modules required with this
const nodeRequire = require;

function getRealmConstructor(environment) {
  switch (environment) {
    case "node.js":
    case "electron":
      return nodeRequire("bindings")("realm.node").Realm;
  }
}
```
Version 0.11.11 of esbuild removed this warning, which means people no longer have a way to know at compile time whether their bundle is broken in this way. Now that esbuild has custom log message levels, this warning can be added back in a way that should make both people happy. With this release, there is now a log message for this that defaults to the debug log level, which normally isn't visible. You can either do --log-override:indirect-require=warning to make this log message a warning (and therefore visible) or use --log-level=debug to see this and all other debug log messages.

`v0.14.42`

Compare Source

Fix a parser hang on invalid CSS (#2276)

Previously invalid CSS with unbalanced parentheses could cause esbuild's CSS parser to hang. An example of such an input is the CSS file :x(. This hang has been fixed.
Add support for custom log message levels

This release allows you to override the default log level of esbuild's individual log messages. For example, CSS syntax errors are treated as warnings instead of errors by default because CSS grammar allows for rules containing syntax errors to be ignored. However, if you would like for esbuild to consider CSS syntax errors to be build errors, you can now configure that like this:
- CLI
```
$ esbuild example.css --log-override:css-syntax-error=error
```
- JS API
```
let result = await esbuild.build({
  entryPoints: ['example.css'],
  logOverride: {
    'css-syntax-error': 'error',
  },
})
```
- Go API
```
result := api.Build(api.BuildOptions{
  EntryPoints: []string{"example.ts"},
  LogOverride: map[string]api.LogLevel{
    "css-syntax-error": api.LogLevelError,
  },
})
```
You can also now use this feature to silence warnings that you are not interested in. Log messages are referred to by their identifier. Each identifier is stable (i.e. shouldn't change over time) except there is no guarantee that the log message will continue to exist. A given log message may potentially be removed in the future, in which case esbuild will ignore log levels set for that identifier. The current list of supported log level identifiers for use with this feature can be found below:

JavaScript:
- assign-to-constant
- call-import-namespace
- commonjs-variable-in-esm
- delete-super-property
- direct-eval
- duplicate-case
- duplicate-object-key
- empty-import-meta
- equals-nan
- equals-negative-zero
- equals-new-object
- html-comment-in-js
- impossible-typeof
- private-name-will-throw
- semicolon-after-return
- suspicious-boolean-not
- this-is-undefined-in-esm
- unsupported-dynamic-import
- unsupported-jsx-comment
- unsupported-regexp
- unsupported-require-call
CSS:
- css-syntax-error
- invalid-@charset
- invalid-@import
- invalid-@nest
- invalid-@layer
- invalid-calc
- js-comment-in-css
- unsupported-@charset
- unsupported-@namespace
- unsupported-css-property
Bundler:
- different-path-case
- ignored-bare-import
- ignored-dynamic-import
- import-is-undefined
- package.json
- require-resolve-not-external
- tsconfig.json
Source maps:
- invalid-source-mappings
- sections-in-source-map
- missing-source-map
- unsupported-source-map-comment
Documentation about which identifiers correspond to which log messages will be added in the future, but hasn't been written yet. Note that it's not possible to configure the log level for a build error. This is by design because changing that would cause esbuild to incorrectly proceed in the building process generate invalid build output. You can only configure the log level for non-error log messages (although you can turn non-errors into errors).

`v0.14.41`

Compare Source

Fix a minification regression in 0.14.40 (#2270, #2271, #2273)

Version 0.14.40 substituted string property keys with numeric property keys if the number has the same string representation as the original string. This was done in three places: computed member expressions, object literal properties, and class fields. However, negative numbers are only valid in computed member expressions while esbuild incorrectly applied this substitution for negative numbers in all places. This release fixes the regression by only doing this substitution for negative numbers in computed member expressions.

This fix was contributed by @susiwen8.

`v0.14.40`

Compare Source

Correct esbuild's implementation of "preserveValueImports": true (#2268)

TypeScript's preserveValueImports setting tells the compiler to preserve unused imports, which can sometimes be necessary because otherwise TypeScript will remove unused imports as it assumes they are type annotations. This setting is useful for programming environments that strip TypeScript types as part of a larger code transformation where additional code is appended later that will then make use of those unused imports, such as with Svelte or Vue.

This release fixes an issue where esbuild's implementation of preserveValueImports diverged from the official TypeScript compiler. If the import clause is present but empty of values (even if it contains types), then the import clause should be considered a type-only import clause. This was an oversight, and has

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

Oct 07 '21 10:10 renovate[bot]

Codecov Report

Merging #4735 (3d92a92) into next (ec17787) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             next    #4735   +/-   ##
=======================================
  Coverage   16.66%   16.66%           
=======================================
  Files           5        5           
  Lines         156      156           
  Branches       32       32           
=======================================
  Hits           26       26           
  Misses        124      124           
  Partials        6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Oct 07 '21 11:10 codecov[bot]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (~0.15.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

Sep 01 '22 03:09 renovate[bot]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Sep 02 '23 00:09 github-actions[bot]

ant-design-vue
ant-design-vue copied to clipboard

chore(deps): update dependency esbuild to ~0.14.0

Release Notes

`v0.14.54`

`v0.14.53`

`v0.14.52`

`v0.14.51`

`v0.14.50`

`v0.14.49`

`v0.14.48`

`v0.14.47`

`v0.14.46`

`v0.14.45`

`v0.14.44`

`v0.14.43`

`v0.14.42`

`v0.14.41`

`v0.14.40`

Configuration

Codecov Report

Renovate Ignore Notification

ant-design-vue ant-design-vue copied to clipboard

chore(deps): update dependency esbuild to ~0.14.0

Release Notes

Configuration

Codecov Report

Renovate Ignore Notification

ant-design-vue
ant-design-vue copied to clipboard