Bump esbuild-linux-64 from 0.14.43 to 0.14.46

Bumps esbuild-linux-64 from 0.14.43 to 0.14.46.

Release notes

Sourced from esbuild-linux-64's releases.

v0.14.46

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

... (truncated)

Changelog

Sourced from esbuild-linux-64's changelog.

0.14.46

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

... (truncated)

Commits

de70834 publish 0.14.46 to npm
7034fca fix #2330: implement extends after infer in ts
465ae2a convert an if to a switch
d981064 make to go formatter happy
0d4fae1 fix #2060: undo the V8 object spread special case
8ff05e1 rename more features
78c7fe4 implement --supports to override syntax features
c090bc4 rename the "bigint" feature
6636f84 merge the "const" and "let" features
ed97dee ignore invalid ts export type * from x (#2329)
Additional commits viewable in compare view

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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

projektwahl / projektwahl-lit

Bump esbuild-linux-64 from 0.14.43 to 0.14.46 #429

v0.14.46

0.14.46