{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":404650460,"defaultBranch":"main","name":"ipyniivue","ownerLogin":"niivue","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2021-09-09T08:49:45.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/80818499?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1725219283.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"3603f8223345774cdd094b4872f000e9576cb813","ref":"refs/heads/dependabot/npm_and_yarn/esbuild-0.23.1","pushedAt":"2024-09-01T19:34:43.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"},"commit":{"message":"Bump esbuild from 0.23.0 to 0.23.1\n\nBumps [esbuild](https://github.com/evanw/esbuild) from 0.23.0 to 0.23.1.\n- [Release notes](https://github.com/evanw/esbuild/releases)\n- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)\n- [Commits](https://github.com/evanw/esbuild/compare/v0.23.0...v0.23.1)\n\n---\nupdated-dependencies:\n- dependency-name: esbuild\n dependency-type: direct:development\n update-type: version-update:semver-patch\n...\n\nSigned-off-by: dependabot[bot] Sourced from esbuild's\r\nreleases. This release deliberately contains backwards-incompatible\r\nchanges. To avoid automatically picking up releases like\r\nthis, you should either be pinning the exact version of\r\n Revert the recent change to avoid bundling dependencies for node (#3819) This release reverts the recent change in version 0.22.0 that made\r\n I've just been made aware that Amazon doesn't pin their dependencies\r\nin their "AWS CDK" product, which means that whenever esbuild\r\npublishes a new release, many people (potentially everyone?) using their\r\nSDK around the world instantly starts using it without Amazon checking\r\nthat it works first. This change in version 0.22.0 happened to break\r\ntheir SDK. I'm amazed that things haven't broken before this point. This\r\nrevert attempts to avoid these problems for Amazon's customers.\r\nHopefully Amazon will pin their dependencies in the future. In addition, this is probably a sign that esbuild is used widely\r\nenough that it now needs to switch to a more complicated release model.\r\nI may have esbuild use a beta channel model for further development. Fix preserving collapsed JSX whitespace (#3818) When transformed, certain whitespace inside JSX elements is ignored\r\ncompletely if it collapses to an empty string. However, the whitespace\r\nshould only be ignored if the JSX is being transformed, not if it's\r\nbeing preserved. This release fixes a bug where esbuild was previously\r\nincorrectly ignoring collapsed whitespace with\r\n // Old output (with --jsx=preserve) // New output (with --jsx=preserve)Release notes
\r\n\r\n
v0.23.0
\r\nesbuild
in your package.json
file\r\n(recommended) or be using a version range syntax that only accepts patch\r\nupgrades such as ^0.22.0
or ~0.22.0
. See npm's\r\ndocumentation about semver for\r\nmore information.\r\n
--packages=external
the default behavior with\r\n--platform=node
. The default is now back to\r\n--packages=bundle
.--jsx=preserve
. Here is an example:// Original code\r\n<Foo>\r\n <Bar />\r\n</Foo>\r\n
\r\n<Foo><Bar /></Foo>;
\r\n<Foo>
\r\n<Bar />
\r\n</Foo>;
\r\n
This release deliberately contains backwards-incompatible\r\nchanges. To avoid automatically picking up releases like this,\r\nyou should either be pinning the exact version of esbuild
\r\nin your package.json
file (recommended) or be using a\r\nversion range syntax that only accepts patch upgrades such as\r\n^0.21.0
or ~0.21.0
. See npm's documentation\r\nabout semver for\r\nmore information.
Omit packages from bundles by default when targeting node (#1874,\r\n#2830,\r\n#2846,\r\n#2915,\r\n#3145,\r\n#3294,\r\n#3323,\r\n#3582,\r\n#3809,\r\n#3815)
\r\nThis breaking change is an experiment. People are commonly confused\r\nwhen using esbuild to bundle code for node (i.e. for\r\n--platform=node
) because some packages may not be intended\r\nfor bundlers, and may use node-specific features that don't work with a\r\nbundler. Even though esbuild's "getting started" instructions\r\nsay to use --packages=external
to work around this problem,\r\nmany people don't read the documentation and don't do this, and are then\r\nconfused when it doesn't work. So arguably this is a bad default\r\nbehavior for esbuild to have if people keep tripping over this.
With this release, esbuild will now omit packages from the bundle by\r\ndefault when the platform is node
(i.e. the previous\r\nbehavior of --packages=external
is now the default in this\r\ncase). Note that your dependencies must now be present on the file\r\nsystem when your bundle is run. If you don't want this behavior,\r\nyou can do --packages=bundle
to allow packages to be\r\nincluded in the bundle (i.e. the previous default behavior). Note that\r\n--packages=bundle
doesn't mean all packages are bundled,\r\njust that packages are allowed to be bundled. You can still exclude\r\nindividual packages from the bundle using --external:
even\r\nwhen --packages=bundle
is present.
The --packages=
setting considers all import paths that\r\n"look like" package imports in the original source code to be\r\npackage imports. Specifically import paths that don't start with a path\r\nsegment of /
or .
or ..
are\r\nconsidered to be package imports. The only two exceptions to this rule\r\nare subpath\r\nimports (which start with a #
character) and TypeScript\r\npath remappings via paths
and/or baseUrl
in\r\ntsconfig.json
(which are applied first).
Drop support for older platforms (#3802)
\r\nThis release drops support for the following operating systems:
\r\n... (truncated)
\r\n\r\nSourced from esbuild's\r\nchangelog.
\r\n\r\n\r\n0.23.0
\r\nThis release deliberately contains backwards-incompatible\r\nchanges. To avoid automatically picking up releases like\r\nthis, you should either be pinning the exact version of\r\n
\r\nesbuild
in yourpackage.json
file\r\n(recommended) or be using a version range syntax that only accepts patch\r\nupgrades such as^0.22.0
or~0.22.0
. See npm's\r\ndocumentation about semver for\r\nmore information.\r\n
\r\n- \r\n
\r\nRevert the recent change to avoid bundling dependencies for node (#3819)
\r\nThis release reverts the recent change in version 0.22.0 that made\r\n
\r\n--packages=external
the default behavior with\r\n--platform=node
. The default is now back to\r\n--packages=bundle
.I've just been made aware that Amazon doesn't pin their dependencies\r\nin their "AWS CDK" product, which means that whenever esbuild\r\npublishes a new release, many people (potentially everyone?) using their\r\nSDK around the world instantly starts using it without Amazon checking\r\nthat it works first. This change in version 0.22.0 happened to break\r\ntheir SDK. I'm amazed that things haven't broken before this point. This\r\nrevert attempts to avoid these problems for Amazon's customers.\r\nHopefully Amazon will pin their dependencies in the future.
\r\nIn addition, this is probably a sign that esbuild is used widely\r\nenough that it now needs to switch to a more complicated release model.\r\nI may have esbuild use a beta channel model for further development.
\r\n- \r\n
\r\nFix preserving collapsed JSX whitespace (#3818)
\r\nWhen transformed, certain whitespace inside JSX elements is ignored\r\ncompletely if it collapses to an empty string. However, the whitespace\r\nshould only be ignored if the JSX is being transformed, not if it's\r\nbeing preserved. This release fixes a bug where esbuild was previously\r\nincorrectly ignoring collapsed whitespace with\r\n
\r\n--jsx=preserve
. Here is an example:\r\n// Original code\r\n<Foo>\r\n <Bar />\r\n</Foo>\r\n
// Old output (with --jsx=preserve)
\r\n
\r\n<Foo><Bar /></Foo>;// New output (with --jsx=preserve)
\r\n<Foo>
\r\n<Bar />
\r\n</Foo>;
\r\n0.22.0
\r\nThis release deliberately contains backwards-incompatible\r\nchanges. To avoid automatically picking up releases like this,\r\nyou should either be pinning the exact version of
\r\nesbuild
\r\nin yourpackage.json
file (recommended) or be using a\r\nversion range syntax that only accepts patch upgrades such as\r\n^0.21.0
or~0.21.0
. See npm's documentation\r\nabout semver for\r\nmore information.\r\n
\r\n\r\n- \r\n
\r\nOmit packages from bundles by default when targeting node (#1874,\r\n#2830,\r\n#2846,\r\n#2915,\r\n#3145,\r\n#3294,\r\n#3323,\r\n#3582,\r\n#3809,\r\n#3815)
\r\nThis breaking change is an experiment. People are commonly confused\r\nwhen using esbuild to bundle code for node (i.e. for\r\n
\r\n--platform=node
) because some packages may not be intended\r\nfor bundlers, and may use node-specific features that don't work with a\r\nbundler. Even though esbuild's "getting started" instructions\r\nsay to use--packages=external
to work around this problem,\r\nmany people don't read the documentation and don't do this, and are then\r\nconfused when it doesn't work. So arguably this is a bad default\r\nbehavior for esbuild to have if people keep tripping over this.With this release, esbuild will now omit packages from the bundle by\r\ndefault when the platform is
\r\nnode
(i.e. the previous\r\nbehavior of--packages=external
is now the default in this\r\ncase). Note that your dependencies must now be present on the file\r\nsystem when your bundle is run. If you don't want this behavior,\r\nyou can do--packages=bundle
to allow packages to be\r\nincluded in the bundle (i.e. the previous default behavior). Note that\r\n--packages=bundle
doesn't mean all packages are bundled,\r\njust that packages are allowed to be bundled. You can still exclude\r\nindividual packages from the bundle using--external:
even\r\nwhen--packages=bundle
is present.The
\r\n--packages=
setting considers all import paths that\r\n"look like" package imports in the original source code to be\r\npackage imports. Specifically import paths that don't start with a path\r\nsegment of/
or.
or..
are\r\nconsidered to be package imports. The only two exceptions to this rule\r\nare subpath\r\nimports (which start with a#
character) and TypeScript\r\npath remappings viapaths
and/orbaseUrl
in\r\ntsconfig.json
(which are applied first).- \r\n
\r\nDrop support for older platforms (#3802)
\r\nThis release drops support for the following operating systems:
\r\n\r\n
\r\n- Windows 7
\r\n- Windows 8
\r\n- Windows Server 2008
\r\n
... (truncated)
\r\n9d50680
\r\npublish 0.23.0 to npmac7fd04
\r\nRevert "fix #1874:\r\nnode defaults to --packages=external
" (#3820)626ac2c
\r\nfix #3818:\r\npreserve collapsed jsx whitespace7c2eb2e
\r\nhashbang syntax is part of es202380c6e6e
\r\npublish 0.22.0 to npm196dcad
\r\nfix #1874:\r\nnode defaults to --packages=external
3f57db8
\r\nrelease notes for #353991663db
\r\nProvide API to create a custom esbuild CLI with plugins (#3539)e01c0e0
\r\nalso mention #3665\r\nin release notes65711b3
\r\nrelease notes for #3674Sourced from esbuild's\r\nreleases.
\r\n\r\n\r\nv0.21.4
\r\n\r\n
\r\n\r\n- \r\n
\r\nUpdate support for import assertions and import attributes in node\r\n(#3778)
\r\nImport assertions (the
\r\nassert
keyword) have been removed\r\nfrom node starting in v22.0.0. So esbuild will now strip them and\r\ngenerate a warning with--target=node22
or above:\r\n▲ [WARNING] The "assert" keyword is not supported\r\nin the configured target environment ("node22")\r\n[assert-to-with]\r\n
\r\nexample.mjs:1:40:\r\n1 │ import json from "esbuild/package.json" assert {\r\ntype: "json" }\r\n │ ~~~~~~\r\n ╵ with\r\n
Did you mean to use "with" instead of "assert"?\r\n
Import attributes (the
\r\nwith
keyword) have been\r\nbackported to node 18 starting in v18.20.0. So esbuild will no longer\r\nstrip them with--target=node18.N
ifN
is 20\r\nor greater.- \r\n
\r\nFix
\r\nfor await
transform when a label is presentThis release fixes a bug where the
\r\nfor await
transform,\r\nwhich wraps the loop in atry
statement, previously failed\r\nto also move the loop's label into thetry
statement. This\r\nbug only affects code that uses both of these features in combination.\r\nHere's an example of some affected code:\r\n// Original code\r\nasync function test() {\r\n outer: for await (const x of [Promise.resolve([0, 1])]) {\r\n for (const y of x) if (y) break outer\r\n throw 'fail'\r\n }\r\n}\r\n
// Old output (with --target=es6)\r\nfunction test() {\r\nreturn __async(this, null, function* () {\r\nouter: try {\r\nfor (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp,\r\nerror; more = !(temp = yield iter.next()).done; more = false) {\r\nconst x = temp.value;\r\nfor (const y of x) if (y) break outer;\r\nthrow "fail";\r\n}\r\n} catch (temp) {\r\nerror = [temp];\r\n} finally {\r\ntry {\r\nmore && (temp = iter.return) && (yield temp.call(iter));\r\n} finally {\r\nif (error)\r\nthrow error[0];\r\n}\r\n}\r\n
... (truncated)
\r\nSourced from esbuild's\r\nchangelog.
\r\n\r\n\r\n0.21.4
\r\n\r\n
\r\n\r\n- \r\n
\r\nUpdate support for import assertions and import attributes in node\r\n(#3778)
\r\nImport assertions (the
\r\nassert
keyword) have been removed\r\nfrom node starting in v22.0.0. So esbuild will now strip them and\r\ngenerate a warning with--target=node22
or above:\r\n▲ [WARNING] The "assert" keyword is not supported\r\nin the configured target environment ("node22")\r\n[assert-to-with]\r\n
\r\nexample.mjs:1:40:\r\n1 │ import json from "esbuild/package.json" assert {\r\ntype: "json" }\r\n │ ~~~~~~\r\n ╵ with\r\n
Did you mean to use "with" instead of "assert"?\r\n
Import attributes (the
\r\nwith
keyword) have been\r\nbackported to node 18 starting in v18.20.0. So esbuild will no longer\r\nstrip them with--target=node18.N
ifN
is 20\r\nor greater.- \r\n
\r\nFix
\r\nfor await
transform when a label is presentThis release fixes a bug where the
\r\nfor await
transform,\r\nwhich wraps the loop in atry
statement, previously failed\r\nto also move the loop's label into thetry
statement. This\r\nbug only affects code that uses both of these features in combination.\r\nHere's an example of some affected code:\r\n// Original code\r\nasync function test() {\r\n outer: for await (const x of [Promise.resolve([0, 1])]) {\r\n for (const y of x) if (y) break outer\r\n throw 'fail'\r\n }\r\n}\r\n
// Old output (with --target=es6)\r\nfunction test() {\r\nreturn __async(this, null, function* () {\r\nouter: try {\r\nfor (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp,\r\nerror; more = !(temp = yield iter.next()).done; more = false) {\r\nconst x = temp.value;\r\nfor (const y of x) if (y) break outer;\r\nthrow "fail";\r\n}\r\n} catch (temp) {\r\nerror = [temp];\r\n} finally {\r\ntry {\r\nmore && (temp = iter.return) && (yield temp.call(iter));\r\n} finally {\r\nif (error)\r\nthrow error[0];\r\n}\r\n
... (truncated)
\r\n67cbf87
\r\npublish 0.21.4 to npm4ad11c3
\r\nfix #3639,\r\nfix #3646:\r\npass with
to onResolve
516ca31
\r\nfix #3343:\r\nallow bundle-internal string aliases9e2f304
\r\nfix #3416,\r\nfix #3425:\r\nbetter enum constant folding8f1faf7
\r\nimplement late constant-folding for && || ??
7d50a50
\r\nimplement late constant-folding of string enums1b29ac7
\r\nfold equality checks after cross-module inliningd7a8bf3
\r\nformatting support for @position-try
(for #3773)5069410
\r\nfix #3778:\r\nimport assertions/attributes for node11d568c
\r\nrun make update-compat-table