[Snyk] Upgrade esbuild from 0.15.18 to 0.19.12 #170
Conversation
Snyk has created this PR to upgrade esbuild from 0.15.18 to 0.19.12. See this package in npm: https://www.npmjs.com/package/esbuild See this project in Snyk: https://app.snyk.io/org/sammytezzy/project/1e70f5b6-c7c2-487f-819a-c1c9c946cb96?utm_source=github&utm_medium=referral&page=upgrade-pr
|
|
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Type: Enhancement
PR Summary: This pull request updates the esbuild package from version 0.15.18 to 0.19.12. It aims to keep the project's dependencies up-to-date, addressing potential vulnerabilities and ensuring compatibility with the latest features and improvements offered by the esbuild package.
Decision: Comment
📝 Type: 'Enhancement' - not supported yet.
- Sourcery currently only approves 'Typo fix' PRs.
✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.
No details provided.
✅ Small diff: the diff is small enough to approve with confidence.
No details provided.
General suggestions:
- Ensure thorough testing of the build process after upgrading to the new version of esbuild to catch any potential issues caused by breaking changes or new behavior.
- Review the release notes of esbuild from version 0.15.18 to 0.19.12 to understand the new features, bug fixes, and any breaking changes that might affect the project.
- Consider the impact of the upgrade on the project's build performance and bundle size, as esbuild has introduced several optimizations and features in the new versions.
Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade esbuild from 0.15.18 to 0.19.12.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: esbuild
-
0.19.12 - 2024-01-23
-
// Original code
-
-
-
0.19.11 - 2023-12-29
-
// Original code
-
// Original code
-
-
-
0.19.10 - 2023-12-19
-
0.19.9 - 2023-12-10
-
0.19.8 - 2023-11-26
-
-
// This old syntax has always been permitted:
-
// Original code
-
0.19.7 - 2023-11-21
-
0.19.6 - 2023-11-19
-
0.19.5 - 2023-10-17
-
0.19.4 - 2023-09-28
-
0.19.3 - 2023-09-14
-
0.19.2 - 2023-08-14
-
0.19.1 - 2023-08-11
-
0.19.0 - 2023-08-08
-
0.18.20 - 2023-08-08
-
0.18.19 - 2023-08-07
-
0.18.18 - 2023-08-05
-
0.18.17 - 2023-07-26
-
0.18.16 - 2023-07-23
-
0.18.15 - 2023-07-20
-
0.18.14 - 2023-07-18
-
0.18.13 - 2023-07-15
-
0.18.12 - 2023-07-13
-
0.18.11 - 2023-07-01
-
0.18.10 - 2023-06-26
-
0.18.9 - 2023-06-26
-
0.18.8 - 2023-06-25
-
0.18.7 - 2023-06-24
-
0.18.6 - 2023-06-20
-
0.18.5 - 2023-06-20
-
0.18.4 - 2023-06-16
-
0.18.3 - 2023-06-15
-
0.18.2 - 2023-06-13
-
0.18.1 - 2023-06-12
-
0.18.0 - 2023-06-09
-
0.17.19 - 2023-05-13
-
0.17.18 - 2023-04-22
-
0.17.17 - 2023-04-16
-
0.17.16 - 2023-04-10
-
0.17.15 - 2023-04-01
-
0.17.14 - 2023-03-26
-
0.17.13 - 2023-03-24
-
0.17.12 - 2023-03-17
-
0.17.11 - 2023-03-03
-
0.17.10 - 2023-02-20
-
0.17.9 - 2023-02-19
-
0.17.8 - 2023-02-13
-
0.17.7 - 2023-02-09
-
0.17.6 - 2023-02-06
-
0.17.5 - 2023-01-27
-
0.17.4 - 2023-01-22
-
0.17.3 - 2023-01-18
-
0.17.2 - 2023-01-17
-
0.17.1 - 2023-01-16
-
0.17.0 - 2023-01-14
-
0.16.17 - 2023-01-11
-
0.16.16 - 2023-01-08
-
0.16.15 - 2023-01-07
-
0.16.14 - 2023-01-04
-
0.16.13 - 2023-01-02
-
0.16.12 - 2022-12-28
-
0.16.11 - 2022-12-27
-
0.16.10 - 2022-12-19
-
0.16.9 - 2022-12-18
-
0.16.8 - 2022-12-16
-
0.16.7 - 2022-12-14
-
0.16.6 - 2022-12-14
-
0.16.5 - 2022-12-13
-
0.16.4 - 2022-12-10
-
0.16.3 - 2022-12-08
-
0.16.2 - 2022-12-08
-
0.16.1 - 2022-12-07
-
0.16.0 - 2022-12-07
-
0.15.18 - 2022-12-05
from esbuild GitHub release notesThe "preserve" JSX mode now preserves JSX text verbatim (#3605)
The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).
Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
let el =
<a href={'/'} title=''"'> some text
{foo}
more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={
'"}>{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title=''"'> some text
{foo}
more text </a>;
Allow JSX elements as JSX attribute values
JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with
{...}. It looks like this:I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.
Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with
{...}escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.Fix a bug with TypeScript type parsing (#3574)
This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:
Fix TypeScript-specific class transform edge case (#3559)
The previous release introduced an optimization that avoided transforming
super()in the class constructor for TypeScript code compiled withuseDefineForClassFieldsset tofalseif all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are#privateinstance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call tosuper()(sincesuper()is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:class Foo extends Bar {
#private = 1;
public: any;
constructor() {
super();
}
}
// Old output (with esbuild v0.19.9)
class Foo extends Bar {
constructor() {
super();
this.#private = 1;
}
#private;
}
// Old output (with esbuild v0.19.10)
class Foo extends Bar {
constructor() {
this.#private = 1;
super();
}
#private;
}
// New output
class Foo extends Bar {
#private = 1;
constructor() {
super();
}
}
Minifier: allow reording a primitive past a side-effect (#3568)
The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:
function f() {
let x = false;
let y = x;
const boolean = y;
let frag = $.template(
<p contenteditable="<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">boolean</span><span class="pl-kos">}</span></span>">hello world</p>);return frag;
}
// Old output (with --minify)
function f(){const e=!1;return $.template(
<p contenteditable="<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">e</span><span class="pl-kos">}</span></span>">hello world</p>)}// New output (with --minify)
function f(){return $.template('<p contenteditable="false">hello world</p>')}
Minifier: consider properties named using known
Symbolinstances to be side-effect free (#3561)Many things in JavaScript can have side effects including property accesses and ToString operations, so using a symbol such as
Symbol.iteratoras a computed property name is not obviously side-effect free. This release adds a special case for knownSymbolinstances so that they are considered side-effect free when used as property names. For example, this class declaration will now be considered side-effect free:Provide the
stop()API in node to exit esbuild's child process (#3558)You can now call
stop()in esbuild's node API to exit esbuild's child process to reclaim the resources used. It only makes sense to do this for a long-lived node process when you know you will no longer be making any more esbuild API calls. It is not necessary to call this to allow node to exit, and it's advantageous to not call this in between calls to esbuild's API as sharing a single long-lived esbuild child process is more efficient than re-creating a new esbuild child process for every API call. This API call used to exist but was removed in version 0.9.0. This release adds it back due to a user request.Read more
Read more
Add a treemap chart to esbuild's bundle analyzer (#2848)
The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens.
Allow decorators after the
exportkeyword (#104)Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the
exportkeyword. However, the upcoming JavaScript decorators feature also allows decorators to come after theexportkeyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after theexportkeyword too. So esbuild now allows this as well:@decorator export class Foo {}
@decorator export default class Foo {}
// This new syntax is now permitted too:
export @decorator class Foo {}
export default @decorator class Foo {}
In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after
interfaceandexport interfacebut not afterexport default interface).Pretty-print decorators using the same whitespace as the original
When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read:
class Foo {
@a @b @c abc
@x @y @z xyz
}
// Old output
class Foo {
@a
@b
@c
abc;
@x
@y
@z
xyz;
}
// New output
class Foo {
@a @b @c abc;
@x @y @z xyz;
}
Read more
Read more
Read more
Read more
Read more
Commit messages
Package name: esbuild
Cargo.lockfrom CI for PRs vercel/turborepo#3558: put the `stop()` api call backCompare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs