chore(deps): update all non-major dependencies #4601
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.138.0
->^0.152.0
^0.17.14
->^0.18.0
4.3.1
->4.3.6
3.8
->3.11
~4.5.4
->~4.9.0
^0.29.8
->^0.32.0
Release Notes
evanw/esbuild
v0.18.6
Compare Source
Fix tree-shaking of classes with decorators (#3164)
This release fixes a bug where esbuild incorrectly allowed tree-shaking on classes with decorators. Each decorator is a function call, so classes with decorators must never be tree-shaken. This bug was a regression that was unintentionally introduced in version 0.18.2 by the change that enabled tree-shaking of lowered private fields. Previously decorators were always lowered, and esbuild always considered the automatically-generated decorator code to be a side effect. But this is no longer the case now that esbuild analyzes side effects using the AST before lowering takes place. This bug was fixed by considering any decorator a side effect.
Fix a minification bug involving function expressions (#3125)
When minification is enabled, esbuild does limited inlining of
const
symbols at the top of a scope. This release fixes a bug where inlineable symbols were incorrectly removed assuming that they were inlined. They may not be inlined in cases where they were referenced by earlier constants in the body of a function expression. The declarations involved in these edge cases are now kept instead of being removed:v0.18.5
Compare Source
Implement auto accessors (#3009)
This release implements the new auto-accessor syntax from the upcoming JavaScript decorators proposal. The auto-accessor syntax looks like this:
This syntax is not yet a part of JavaScript but it was added to TypeScript in version 4.9. More information about this feature can be found in microsoft/TypeScript#49705. Auto-accessors will be transformed if the target is set to something other than
esnext
:You can also now use auto-accessors with esbuild's TypeScript experimental decorator transformation, which should behave the same as decorating the underlying getter/setter pair.
Please keep in mind that this syntax is not yet part of JavaScript. This release enables auto-accessors in
.js
files with the expectation that it will be a part of JavaScript soon. However, esbuild may change or remove this feature in the future if JavaScript ends up changing or removing this feature. Use this feature with caution for now.Pass through JavaScript decorators (#104)
In this release, esbuild now parses decorators from the upcoming JavaScript decorators proposal and passes them through to the output unmodified (as long as the language target is set to
esnext
). Transforming JavaScript decorators to environments that don't support them has not been implemented yet. The only decorator transform that esbuild currently implements is still the TypeScript experimental decorator transform, which only works in.ts
files and which requires"experimentalDecorators": true
in yourtsconfig.json
file.Static fields with assign semantics now use static blocks if possible
Setting
useDefineForClassFields
to false in TypeScript requires rewriting class fields to assignment statements. Previously this was done by removing the field from the class body and adding an assignment statement after the class declaration. However, this also caused any private fields to also be lowered by necessity (in case a field initializer uses a private symbol, either directly or indirectly). This release changes this transform to use an inline static block if it's supported, which avoids needing to lower private fields in this scenario:Fix TypeScript experimental decorators combined with
--mangle-props
(#3177)Previously using TypeScript experimental decorators combined with the
--mangle-props
setting could result in a crash, as the experimental decorator transform was not expecting a mangled property as a class member. This release fixes the crash so you can now combine both of these features together safely.v0.18.4
Compare Source
Bundling no longer unnecessarily transforms class syntax (#1360, #1328, #1524, #2416)
When bundling, esbuild automatically converts top-level class statements to class expressions. Previously this conversion had the unfortunate side-effect of also transforming certain other class-related syntax features to avoid correctness issues when the references to the class name within the class body. This conversion has been reworked to avoid doing this:
This conversion process is very complicated and has many edge cases (including interactions with static fields, static blocks, private class properties, and TypeScript experimental decorators). It should already be pretty robust but a change like this may introduce new unintentional behavior. Please report any issues with this upgrade on the esbuild bug tracker.
You may be wondering why esbuild needs to do this at all. One reason to do this is that esbuild's bundler sometimes needs to lazily-evaluate a module. For example, a module may end up being both the target of a dynamic
import()
call and a staticimport
statement. Lazy module evaluation is done by wrapping the top-level module code in a closure. To avoid a performance hit for staticimport
statements, esbuild stores top-level exported symbols outside of the closure and references them directly instead of indirectly.Another reason to do this is that multiple JavaScript VMs have had and continue to have performance issues with TDZ (i.e. "temporal dead zone") checks. These checks validate that a let, or const, or class symbol isn't used before it's initialized. Here are two issues with well-known VMs:
JavaScriptCore had a severe performance issue as their TDZ implementation had time complexity that was quadratic in the number of variables needing TDZ checks in the same scope (with the top-level scope typically being the worst offender). V8 has ongoing issues with TDZ checks being present throughout the code their JIT generates even when they have already been checked earlier in the same function or when the function in question has already been run (so the checks have already happened).
Due to esbuild's parallel architecture, esbuild both a) needs to convert class statements into class expressions during parsing and b) doesn't yet know whether this module will need to be lazily-evaluated or not in the parser. So esbuild always does this conversion during bundling in case it's needed for correctness (and also to avoid potentially catastrophic performance issues due to bundling creating a large scope with many TDZ variables).
Enforce TDZ errors in computed class property keys (#2045)
JavaScript allows class property keys to be generated at run-time using code, like this:
Previously esbuild treated references to the containing class name within computed property keys as a reference to the partially-initialized class object. That meant code that attempted to reference properties of the class object (such as the code above) would get back
undefined
instead of throwing an error.This release rewrites references to the containing class name within computed property keys into code that always throws an error at run-time, which is how this JavaScript code is supposed to work. Code that does this will now also generate a warning. You should never write code like this, but it now should be more obvious when incorrect code like this is written.
Fix an issue with experimental decorators and static fields (#2629)
This release also fixes a bug regarding TypeScript experimental decorators and static class fields which reference the enclosing class name in their initializer. This affected top-level classes when bundling was enabled. Previously code that does this could crash because the class name wasn't initialized yet. This case should now be handled correctly:
Fix a minification regression with negative numeric properties (#3169)
Version 0.18.0 introduced a regression where computed properties with negative numbers were incorrectly shortened into a non-computed property when minification was enabled. This regression has been fixed:
v0.18.3
Compare Source
Fix a panic due to empty static class blocks (#3161)
This release fixes a bug where an internal invariant that was introduced in the previous release was sometimes violated, which then caused a panic. It happened when bundling code containing an empty static class block with both minification and bundling enabled.
v0.18.2
Compare Source
Lower static blocks when static fields are lowered (#2800, #2950, #3025)
This release fixes a bug where esbuild incorrectly did not lower static class blocks when static class fields needed to be lowered. For example, the following code should print
1 2 3
but previously printed2 1 3
instead due to this bug:Use static blocks to implement
--keep-names
on classes (#2389)This change fixes a bug where the
name
property could previously be incorrect within a class static context when using--keep-names
. The problem was that thename
property was being initialized after static blocks were run instead of before. This has been fixed by moving thename
property initializer into a static block at the top of the class body:This change was somewhat involved, especially regarding what esbuild considers to be side-effect free. Some unused classes that weren't removed by tree shaking in previous versions of esbuild may now be tree-shaken. One example is classes with static private fields that are transformed by esbuild into code that doesn't use JavaScript's private field syntax. Previously esbuild's tree shaking analysis ran on the class after syntax lowering, but with this release it will run on the class before syntax lowering, meaning it should no longer be confused by class mutations resulting from automatically-generated syntax lowering code.
v0.18.1
Compare Source
Fill in
null
entries in input source maps (#3144)If esbuild bundles input files with source maps and those source maps contain a
sourcesContent
array withnull
entries, esbuild previously copied thosenull
entries over to the output source map. With this release, esbuild will now attempt to fill in thosenull
entries by looking for a file on the file system with the corresponding name from thesources
array. This matches esbuild's existing behavior that automatically generates thesourcesContent
array from the file system if the entiresourcesContent
array is missing.Support
/* @​__KEY__ */
comments for mangling property names (#2574)Property mangling is an advanced feature that enables esbuild to minify certain property names, even though it's not possible to automatically determine that it's safe to do so. The safe property names are configured via regular expression such as
--mangle-props=_$
(mangle all properties ending in_
).Sometimes it's desirable to also minify strings containing property names, even though it's not possible to automatically determine which strings are property names. This release makes it possible to do this by annotating those strings with
/* @​__KEY__ */
. This is a convention that Terser added earlier this year, and which esbuild is now following too: https://github.com/terser/terser/pull/1365. Using it looks like this:Support
/* @​__NO_SIDE_EFFECTS__ */
comments for functions (#3149)Rollup has recently added support for
/* @​__NO_SIDE_EFFECTS__ */
annotations before functions to indicate that calls to these functions can be removed if the result is unused (i.e. the calls can be assumed to have no side effects). This release adds basic support for these to esbuild as well, which means esbuild will now parse these comments in input files and preserve them in output files. This should help people that use esbuild in combination with Rollup.Note that this doesn't necessarily mean esbuild will treat these calls as having no side effects, as esbuild's parallel architecture currently isn't set up to enable this type of cross-file tree-shaking information (tree-shaking decisions regarding a function call are currently local to the file they appear in). If you want esbuild to consider a function call to have no side effects, make sure you continue to annotate the function call with
/* @​__PURE__ */
(which is the previously-established convention for communicating this).v0.18.0
Compare Source
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 yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.17.0
or~0.17.0
. See npm's documentation about semver for more information.The breaking changes in this release mainly focus on fixing some long-standing issues with esbuild's handling of
tsconfig.json
files. Here are all the changes in this release, in detail:Add a way to try esbuild online (#797)
There is now a way to try esbuild live on esbuild's website without installing it: https://esbuild.github.io/try/. In addition to being able to more easily evaluate esbuild, this should also make it more efficient to generate esbuild bug reports. For example, you can use it to compare the behavior of different versions of esbuild on the same input. The state of the page is stored in the URL for easy sharing. Many thanks to @hyrious for creating https://hyrious.me/esbuild-repl/, which was the main inspiration for this addition to esbuild's website.
Two forms of build options are supported: either CLI-style (example) or JS-style (example). Both are converted into a JS object that's passed to esbuild's WebAssembly API. The CLI-style argument parser is a custom one that simulates shell quoting rules, and the JS-style argument parser is also custom and parses a superset of JSON (basically JSON5 + regular expressions). So argument parsing is an approximate simulation of what happens for real but hopefully it should be close enough.
Changes to esbuild's
tsconfig.json
support (#3019):This release makes the following changes to esbuild's
tsconfig.json
support:Using experimental decorators now requires
"experimentalDecorators": true
(#104)Previously esbuild would always compile decorators in TypeScript code using TypeScript's experimental decorator transform. Now that standard JavaScript decorators are close to being finalized, esbuild will now require you to use
"experimentalDecorators": true
to do this. This new requirement makes it possible for esbuild to introduce a transform for standard JavaScript decorators in TypeScript code in the future. Such a transform has not been implemented yet, however.TypeScript's
target
no longer affects esbuild'starget
(#2628)Some people requested that esbuild support TypeScript's
target
setting, so support for it was added (in version 0.12.4). However, esbuild supports reading from multipletsconfig.json
files within a single build, which opens up the possibility that different files in the build have different language targets configured. There isn't really any reason to do this and it can lead to unexpected results. So with this release, thetarget
setting intsconfig.json
will no longer affect esbuild's owntarget
setting. You will have to use esbuild's own target setting instead (which is a single, global value).TypeScript's
jsx
setting no longer causes esbuild to preserve JSX syntax (#2634)TypeScript has a setting called
jsx
that controls how to transform JSX into JS. The tool-agnostic transform is calledreact
, and the React-specific transform is calledreact-jsx
(orreact-jsxdev
). There is also a setting calledpreserve
which indicates JSX should be passed through untransformed. Previously people would run esbuild with"jsx": "preserve"
in theirtsconfig.json
files and then be surprised when esbuild preserved their JSX. So with this release, esbuild will now ignore"jsx": "preserve"
intsconfig.json
files. If you want to preserve JSX syntax with esbuild, you now have to use--jsx=preserve
.Note: Some people have suggested that esbuild's equivalent
jsx
setting override the one intsconfig.json
. However, some projects need to legitimately have different files within the same build use different transforms (i.e.react
vs.react-jsx
) and having esbuild's globaljsx
setting overridetsconfig.json
would prevent this from working. This release ignores"jsx": "preserve"
but still allows otherjsx
values intsconfig.json
files to override esbuild's globaljsx
setting to keep the ability for multiple files within the same build to use different transforms.useDefineForClassFields
behavior has changed (#2584, #2993)Class fields in TypeScript look like this (
x
is a class field):TypeScript has legacy behavior that uses assignment semantics instead of define semantics for class fields when
useDefineForClassFields
is enabled (in which case class fields in TypeScript behave differently than they do in JavaScript, which is arguably "wrong").This legacy behavior exists because TypeScript added class fields to TypeScript before they were added to JavaScript. The TypeScript team decided to go with assignment semantics and shipped their implementation. Much later on TC39 decided to go with define semantics for class fields in JavaScript instead. This behaves differently if the base class has a setter with the same name:
When you run
tsc
, the value ofuseDefineForClassFields
defaults tofalse
when it's not specified and thetarget
intsconfig.json
is present but earlier thanES2022
. This sort of makes sense because the class field language feature was added in ES2022, so before ES2022 class fields didn't exist (and thus TypeScript's legacy behavior is active). However, TypeScript'starget
setting currently defaults toES3
which unfortunately means that theuseDefineForClassFields
setting currently defaults to false (i.e. to "wrong"). In other words if you runtsc
with all default settings, class fields will behave incorrectly.Previously esbuild tried to do what
tsc
did. That meant esbuild's version ofuseDefineForClassFields
wasfalse
by default, and was alsofalse
if esbuild's--target=
was present but earlier thanes2022
. However, TypeScript's legacy class field behavior is becoming increasingly irrelevant and people who expect class fields in TypeScript to work like they do in JavaScript are confused when they use esbuild with default settings. It's also confusing that the behavior of class fields would change if you changed the language target (even though that's exactly how TypeScript works).So with this release, esbuild will now only use the information in
tsconfig.json
to determine whetheruseDefineForClassFields
is true or not. SpecificallyuseDefineForClassFields
will be respected if present, otherwise it will befalse
iftarget
is present intsconfig.json
and isES2021
or earlier, otherwise it will betrue
. Targets passed to esbuild's--target=
setting will no longer affectuseDefineForClassFields
.Note that this means different directories in your build can have different values for this setting since esbuild allows different directories to have different
tsconfig.json
files within the same build. This should let you migrate your code one directory at a time without esbuild's--target=
setting affecting the semantics of your code.Add support for
verbatimModuleSyntax
from TypeScript 5.0TypeScript 5.0 added a new option called
verbatimModuleSyntax
that deprecates and replaces two older options,preserveValueImports
andimportsNotUsedAsValues
. SettingverbatimModuleSyntax
to true intsconfig.json
tells esbuild to not drop unused import statements. Specifically esbuild now treats"verbatimModuleSyntax": true
as if you had specified both"preserveValueImports": true
and"importsNotUsedAsValues": "preserve"
.Add multiple inheritance for
tsconfig.json
from TypeScript 5.0TypeScript 5.0 now allows multiple inheritance for
tsconfig.json
files. You can now pass an array of filenames via theextends
parameter and yourtsconfig.json
will start off containing properties from all of those configuration files, in order. This release of esbuild adds support for this new TypeScript feature.Remove support for
moduleSuffixes
(#2395)The community has requested that esbuild remove support for TypeScript's
moduleSuffixes
feature, so it has been removed in this release. Instead you can use esbuild's--resolve-extensions=
feature to select which module suffix you want to build with.Apply
--tsconfig=
overrides tostdin
and virtual files (#385, #2543)When you override esbuild's automatic
tsconfig.json
file detection with--tsconfig=
to pass a specifictsconfig.json
file, esbuild previously didn't apply these settings to source code passed via thestdin
API option or to TypeScript files from plugins that weren't in thefile
namespace. This release changes esbuild's behavior so that settings fromtsconfig.json
also apply to these source code files as well.Support
--tsconfig-raw=
in build API calls (#943, #2440)Previously if you wanted to override esbuild's automatic
tsconfig.json
file detection, you had to create a newtsconfig.json
file and pass the file name to esbuild via the--tsconfig=
flag. With this release, you can now optionally use--tsconfig-raw=
instead to pass the contents oftsconfig.json
to esbuild directly instead of passing the file name. For example, you can now use--tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}}
to enable TypeScript experimental decorators directly using a command-line flag (assuming you escape the quotes correctly using your current shell's quoting rules). The--tsconfig-raw=
flag previously only worked with transform API calls but with this release, it now works with build API calls too.Ignore all
tsconfig.json
files innode_modules
(#276, #2386)This changes esbuild's behavior that applies
tsconfig.json
to all files in the subtree of the directory containingtsconfig.json
. In version 0.12.7, esbuild started ignoringtsconfig.json
files insidenode_modules
folders. The rationale is that people typically do this by mistake and that doing this intentionally is a rare use case that doesn't need to be supported. However, this change only applied to certain syntax-specific settings (e.g.jsxFactory
) but did not apply to path resolution settings (e.g.paths
). With this release, esbuild will now ignore alltsconfig.json
files innode_modules
instead of only ignoring certain settings.Ignore
tsconfig.json
when resolving paths withinnode_modules
(#2481)Previously fields in
tsconfig.json
related to path resolution (e.g.paths
) were respected for all files in the subtree containing thattsconfig.json
file, even within a nestednode_modules
subdirectory. This meant that a project'spaths
settings could potentially affect any bundled packages. With this release, esbuild will no longer usetsconfig.json
settings during path resolution inside nestednode_modules
subdirectories.Prefer
.js
over.ts
withinnode_modules
(#3019)The default list of implicit extensions that esbuild will try appending to import paths contains
.ts
before.js
. This makes it possible to bundle TypeScript projects that reference other files in the project using extension-less imports (e.g../some-file
to load./some-file.ts
instead of./some-file.js
). However, this behavior is undesirable withinnode_modules
directories. Some package authors publish both their original TypeScript code and their compiled JavaScript code side-by-side. In these cases, esbuild should arguably be using the compiled JavaScript files instead of the original TypeScript files because the TypeScript compilation settings for files within the package should be determined by the package author, not the user of esbuild. So with this release, esbuild will now prefer implicit.js
extensions over.ts
when searching for import paths withinnode_modules
.These changes are intended to improve esbuild's compatibility with
tsc
and reduce the number of unfortunate behaviors regardingtsconfig.json
and esbuild.Add a workaround for bugs in Safari 16.2 and earlier (#3072)
Safari's JavaScript parser had a bug (which has now been fixed) where at least something about unary/binary operators nested inside default arguments nested inside either a function or class expression was incorrectly considered a syntax error if that expression was the target of a property assignment. Here are some examples that trigger this Safari bug:
It's not clear what the exact conditions are that trigger this bug. However, a workaround for this bug appears to be to post-process your JavaScript to wrap any in function and class declarations that are the direct target of a property access expression in parentheses. That's the workaround that UglifyJS applies for this issue: mishoo/UglifyJS#2056. So that's what esbuild now does starting with this release:
This fix is not enabled by default. It's only enabled when
--target=
contains Safari 16.2 or earlier, such as with--target=safari16.2
. You can also explicitly enable or disable this specific transform (calledfunction-or-class-property-access
) with--supported:function-or-class-property-access=false
.Fix esbuild's TypeScript type declarations to forbid unknown properties (#3089)
Version 0.17.0 of esbuild introduced a specific form of function overloads in the TypeScript type definitions for esbuild's API calls that looks like this:
This more accurately reflects how esbuild's JavaScript API behaves. The result object returned by
transformSync
only has thelegalComments
property if you passlegalComments: 'external'
:However, this form of function overloads unfortunately allows typos (e.g.
egalComments
) to pass the type checker without generating an error as TypeScript allows all objects with unknown properties to extendTransformOptions
. These typos result in esbuild's API throwing an error at run-time.To prevent typos during type checking, esbuild's TypeScript type definitions will now use a different form that looks like this:
This change should hopefully not affect correct code. It should hopefully introduce type errors only for incorrect code.
Fix CSS nesting transform for pseudo-elements (#3119)
This release fixes esbuild's CSS nesting transform for pseudo-elements (e.g.
::before
and::after
). The CSS nesting specification says that the nesting selector does not work with pseudo-elements. This can be seen in the example below: esbuild does not carry the parent pseudo-element::before
through the nesting selector&
. However, that doesn't apply to pseudo-elements that are within the same selector. Previously esbuild had a bug where it considered pseudo-elements in both locations as invalid. This release changes esbuild to only consider those from the parent selector invalid, which should align with the specification:Forbid
&
before a type selector in nested CSSThe people behind the work-in-progress CSS nesting specification have very recently decided to forbid nested CSS that looks like
&div
. You will have to use eitherdiv&
or&:is(div)
instead. This release of esbuild has been updated to take this new change into consideration. Doing this now generates a warning. The suggested fix is slightly different depending on where in the overall selector it happened:v0.17.19
Compare Source
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:
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:x<y>=a<b<c>>()
x<y>=a();
x=a();
x<y>=a();
x=a()
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 sometimesuse asm
. However, the people behind React have made up their own directive for their own custom dialect of JavaScript. Previously esbuild only preserved theuse 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: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:v0.17.18
Compare Source
Fix non-default JSON import error with
export {} from
(#3070)This release fixes a bug where esbuild incorrectly identified statements of the form
export { default as x } from "y" assert { type: "json" }
as a non-default import. The bug did not affect code of the formimport { default as x } from ...
(only code that used theexport
keyword).Fix a crash with an invalid subpath import (#3067)
Previously esbuild could crash when attempting to generate a friendly error message for an invalid subpath import (i.e. an import starting with
#
). This happened because esbuild originally only supported theexports
field and the code for that error message was not updated when esbuild later added support for theimports
field. This crash has been fixed.v0.17.17
Compare Source
Fix CSS nesting transform for top-level
&
(#3052)Previously esbuild could crash with a stack overflow when lowering CSS nesting rules with a top-level
&
, such as in the code below. This happened because esbuild's CSS nesting transform didn't handle top-level&
, causing esbuild to inline the top-level selector into itself. This release handles top-level&
by replacing it with the:scope
pseudo-class:Support
exports
inpackage.json
forextends
intsconfig.json
(#3058)TypeScript 5.0 added the ability to use
extends
intsconfig.json
to reference a path in a package whosepackage.json
file contains anexports
map that points to the correct location. This doesn't automatically work in esbuild becausetsconfig.json
affects esbuild's path resolution, so esbuild's normal path resolution logic doesn't apply.This release adds support for doing this by adding some additional code that attempts to resolve the
extends
path using theexports
field. The behavior should be similar enough to esbuild's main path resolution logic to work as expected.Note that esbuild always treats this
extends
import as arequire()
import since that's what TypeScript appears to do. Specifically therequire
condition will be active and theimport
condition will be inactive.Fix watch mode with
NODE_PATH
(#3062)Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the
NODE_PATH
environment variable. While esbuild supports this too, previously a bug prevented esbuild's watch mode from picking up changes to imported files that were contained directly in aNODE_PATH
directory. You're supposed to useNODE_PATH
for packages, but some people abuse this feature by putting files in that directory instead (e.g.node_modules/some-file.js
instead ofnode_modules/some-pkg/some-file.js
). The watch mode bug happens when you do this because esbuild first tries to readsome-file.js
as a directory and then as a file. Watch mode was incorrectly waiting forsome-file.js
to become a valid directory. This release fixes this edge case bug by changing watch mode to watchsome-file.js
as a file when this happens.v0.17.16
Compare Source
Fix CSS nesting transform for triple-nested rules that start with a combinator (#3046)
This release fixes a bug with esbuild where triple-nested CSS rules that start with a combinator were not transformed correctly for older browsers. Here's an example of such a case before and after this bug fix:
Support
--inject
with a file loaded using thecopy
loader (#3041)This release now allows you to use
--inject
with a file that is loaded using thecopy
loader. Thecopy
loader copies the imported file to the output directory verbatim and rewrites the path in theimport
statement to point to the copied output file. When used with--inject
, this means the injected file will be copied to the output directory as-is and a bareimport
statement for that file will be inserted in any non-copy output files that esbuild generates.Note that since esbuild doesn't parse the contents of copied files, esbuild will not expose any of the export names as usable imports when you do this (in the way that esbuild's
--inject
feature is typically used). However, any side-effects that the injected file has will still occur.v0.17.15
Compare Source
Allow keywords as type parameter names in mapped types (#3033)
TypeScript allows type keywords to be used as parameter names in mapped types. Previously esbuild incorrectly treated this as an error. Code that does this is now supported:
Add annotations for re-exported modules in node (#2486, #3029)
Node lets you import named imports from a CommonJS module using ESM import syntax. However, the allowed names aren't derived from the properties of the CommonJS module. Instead they are derived from an arbitrary syntax-only analysis of the CommonJS module's JavaScript AST.
To accommodate node doing this, esbuild's ESM-to-CommonJS conversion adds a special non-executable "annotation" for node that describes the exports that node should expose in this scenario. It takes the form
0 && (module.exports = { ... })
and comes at the end of the file (0 && expr
meansexpr
is never evaluated).Previously esbuild didn't do this for modules re-exported using the
export * from
syntax. Annotations for these re-exports will now be added starting with this release:Note that you need to specify both
--format=cjs
and--platform=node
to get these node-specific annotations.Avoid printing an unnecessary space in between a number and a
.
(#3026)JavaScript typically requires a space in between a number token and a
.
tokenConfiguration
📅 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.