Sourced from esbuild's releases.
v0.19.1
Fix a regression with
baseURLintsconfig.json(#3307)The previous release moved
tsconfig.jsonpath resolution before--packages=externalchecks to allow thepathsfield intsconfig.jsonto avoid a package being marked as external. However, that reordering accidentally broke the behavior of thebaseURLfield fromtsconfig.json. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.Parse TypeScript type arguments for JavaScript decorators (#3308)
When parsing JavaScript decorators in TypeScript (i.e. with
experimentalDecoratorsdisabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:@foo<number> @bar<number, string>() class Foo {}Fix glob patterns matching extra stuff at the end (#3306)
Previously glob patterns such as
./*.jswould incorrectly behave like./*.js*during path matching (also matching.js.mapfiles, for example). This was never intentional behavior, and has now been fixed.Change the permissions of esbuild's generated output files (#3285)
This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's
fs.writeFileSyncfunction. Since most tools written in JavaScript usefs.writeFileSync, this should make esbuild more consistent with how other JavaScript build tools behave.The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for
fs.writeFileSyncdefaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.Fix a subtle CSS ordering issue with
@importand@layerWith this release, esbuild may now introduce additional
@layerrules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:/* entry.css */ @import "a.css"; @import "b.css"; @import "a.css";/* a.css */ @layer a { body { background: red; } }/* b.css */ @layer b { body { background: green;
... (truncated)
Sourced from esbuild's changelog.
0.19.1
Fix a regression with
baseURLintsconfig.json(#3307)The previous release moved
tsconfig.jsonpath resolution before--packages=externalchecks to allow thepathsfield intsconfig.jsonto avoid a package being marked as external. However, that reordering accidentally broke the behavior of thebaseURLfield fromtsconfig.json. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.Parse TypeScript type arguments for JavaScript decorators (#3308)
When parsing JavaScript decorators in TypeScript (i.e. with
experimentalDecoratorsdisabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:@foo<number> @bar<number, string>() class Foo {}Fix glob patterns matching extra stuff at the end (#3306)
Previously glob patterns such as
./*.jswould incorrectly behave like./*.js*during path matching (also matching.js.mapfiles, for example). This was never intentional behavior, and has now been fixed.Change the permissions of esbuild's generated output files (#3285)
This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's
fs.writeFileSyncfunction. Since most tools written in JavaScript usefs.writeFileSync, this should make esbuild more consistent with how other JavaScript build tools behave.The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for
fs.writeFileSyncdefaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.Fix a subtle CSS ordering issue with
@importand@layerWith this release, esbuild may now introduce additional
@layerrules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:/* entry.css */ @import "a.css"; @import "b.css"; @import "a.css";/* a.css */ @layer a { body { background: red; } }/* b.css */ @layer b { body {
... (truncated)
49801f7
publish 0.19.1 to npm1fca4aa
fix #3307:
regression with tsconfig baseURLa973f87
fix #3308:
TS type arguments for JS decoratorsbe9e098
fix #3306:
handle lack of a trailing glob wildcard83917cf
css: handle external @import condition chainsd81d759
adjust source range for duplicate case warning4b67d82
tsconfig: options outside compilerOptions (#3301)813fb3a
api: reduce console output when an error is thrownab9007c
fix(TsconfigRaw): baseUrl to be string (#3299)4202ea0
css: fix ordering with @import and @layer