sui
sui copied to clipboard
feat(deps): bump esbuild from 0.15.5 to 0.15.11
Bumps esbuild from 0.15.5 to 0.15.11.
Release notes
Sourced from esbuild's releases.
v0.15.11
Fix various edge cases regarding template tags and
this(#2610)This release fixes some bugs where the value of
thiswasn't correctly preserved when evaluating template tags in a few edge cases. These edge cases are listed below:async function test() { class Foo { foo() { return this } } class Bar extends Foo { a = async () => super.foo`` b = async () => super['foo']`` c = async (foo) => super[foo]`` } function foo() { return this } const obj = { foo } const bar = new Bar console.log( (await bar.a()) === bar, (await bar.b()) === bar, (await bar.c('foo')) === bar, { foo }.foo``.foo === foo, (true && obj.foo)`` !== obj, (false || obj.foo)`` !== obj, (null ?? obj.foo)`` !== obj, ) } test()Each edge case in the code above previously incorrectly printed
falsewhen run through esbuild with--minify --target=es6but now correctly printstrue. These edge cases are unlikely to have affected real-world code.v0.15.10
Add support for node's "pattern trailers" syntax (#2569)
After esbuild implemented node's
exportsfeature inpackage.json, node changed the feature to also allow text after*wildcards in patterns. Previously the*was required to be at the end of the pattern. It lets you do something like this:{ "exports": { "./features/*": "./features/*.js", "./features/*.js": "./features/*.js" } }With this release, esbuild now supports these types of patterns too.
Fix subpath imports with Yarn PnP (#2545)
Node has a little-used feature called subpath imports which are package-internal imports that start with
#and that go through theimportsmap inpackage.json. Previously esbuild had a bug that caused esbuild to not handle these correctly in packages installed via Yarn's "Plug'n'Play" installation strategy. The problem was that subpath imports were being checked after Yarn PnP instead of before. This release reorders these checks, which should allow subpath imports to work in this case.
... (truncated)
Changelog
Sourced from esbuild's changelog.
0.15.11
Fix various edge cases regarding template tags and
this(#2610)This release fixes some bugs where the value of
thiswasn't correctly preserved when evaluating template tags in a few edge cases. These edge cases are listed below:async function test() { class Foo { foo() { return this } } class Bar extends Foo { a = async () => super.foo`` b = async () => super['foo']`` c = async (foo) => super[foo]`` } function foo() { return this } const obj = { foo } const bar = new Bar console.log( (await bar.a()) === bar, (await bar.b()) === bar, (await bar.c('foo')) === bar, { foo }.foo``.foo === foo, (true && obj.foo)`` !== obj, (false || obj.foo)`` !== obj, (null ?? obj.foo)`` !== obj, ) } test()Each edge case in the code above previously incorrectly printed
falsewhen run through esbuild with--minify --target=es6but now correctly printstrue. These edge cases are unlikely to have affected real-world code.0.15.10
Add support for node's "pattern trailers" syntax (#2569)
After esbuild implemented node's
exportsfeature inpackage.json, node changed the feature to also allow text after*wildcards in patterns. Previously the*was required to be at the end of the pattern. It lets you do something like this:{ "exports": { "./features/*": "./features/*.js", "./features/*.js": "./features/*.js" } }With this release, esbuild now supports these types of patterns too.
Fix subpath imports with Yarn PnP (#2545)
... (truncated)
Commits
0bb62e8publish 0.15.11 to npm9c89f14update go 1.19.1 => 1.19.20d8ec0afix #2610: template tag edge cases withthisa4a45f3fix indentation in tests81fa2camore info in yarn pnp error messages (#2585)fdbea94fixes for NewStringInJSLogaaae34epublish 0.15.10 to npm4bd03f3fix #1861, fix #2565: addcssBundleto metafilec55000dFix subpath imports with Yarn PnP (#2547)1bce251fix transform tsconfigRaw type (#2568)- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)