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.
Snyk has created this PR to upgrade multiple dependencies.
👯♂ The following dependencies are linked and will therefore be updated together.ℹ️ 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.
@esbuild/darwin-arm64
from 0.23.0 to 0.23.1 | 1 version ahead of your current version | 24 days ago
on 2024-08-16
@esbuild/linux-x64
from 0.23.0 to 0.23.1 | 1 version ahead of your current version | 24 days ago
on 2024-08-16
@rollup/rollup-darwin-arm64
from 4.20.0 to 4.21.0 | 1 version ahead of your current version | 23 days ago
on 2024-08-18
@rollup/rollup-linux-x64-gnu
from 4.20.0 to 4.21.0 | 1 version ahead of your current version | 23 days ago
on 2024-08-18
@tanstack/react-query
from 5.51.23 to 5.51.24 | 1 version ahead of your current version | 22 days ago
on 2024-08-19
@tanstack/react-query-devtools
from 5.51.23 to 5.51.24 | 1 version ahead of your current version | 22 days ago
on 2024-08-19
@tanstack/react-router
from 1.48.1 to 1.48.4 | 1 version ahead of your current version | 22 days ago
on 2024-08-19
@tanstack/react-virtual
from 3.9.0 to 3.10.1 | 2 versions ahead of your current version | 21 days ago
on 2024-08-20
@tanstack/router-devtools
from 1.48.1 to 1.48.4 | 1 version ahead of your current version | 22 days ago
on 2024-08-19
Release notes
Package name: @esbuild/darwin-arm64
Allow using the
node:
import prefix withes*
targets (#3821)The
node:
prefix on imports is an alternate way to import built-in node modules. For example,import fs from "fs"
can also be writtenimport fs from "node:fs"
. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with--target=node14
so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as--target=node18,es2022
removes thenode:
prefix because none of thees*
targets are known to support this feature. This release adds the support for thenode:
flag to esbuild's internal compatibility table fores*
to allow you to use compound targets like this:import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
Fix a panic when using the CLI with invalid build flags if
--analyze
is present (#3834)Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the
--analyze
flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how--analyze
is implemented) to a null build object. The panic has been fixed in this release.Fix incorrect location of certain error messages (#3845)
This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)
With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
Fix a memory leak with
pluginData
(#3825)With this release, the build context's internal
pluginData
cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that returnpluginData
objects fromonResolve
and/oronLoad
callbacks.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.22.0
or~0.22.0
. See npm's documentation about semver for more information.Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made
--packages=external
the default behavior with--platform=node
. The default is now back to--packages=bundle
.I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I 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 completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with
--jsx=preserve
. Here is an example:<Foo>
<Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;
Package name: @esbuild/linux-x64
Allow using the
node:
import prefix withes*
targets (#3821)The
node:
prefix on imports is an alternate way to import built-in node modules. For example,import fs from "fs"
can also be writtenimport fs from "node:fs"
. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with--target=node14
so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as--target=node18,es2022
removes thenode:
prefix because none of thees*
targets are known to support this feature. This release adds the support for thenode:
flag to esbuild's internal compatibility table fores*
to allow you to use compound targets like this:import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
Fix a panic when using the CLI with invalid build flags if
--analyze
is present (#3834)Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the
--analyze
flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how--analyze
is implemented) to a null build object. The panic has been fixed in this release.Fix incorrect location of certain error messages (#3845)
This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)
With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
Fix a memory leak with
pluginData
(#3825)With this release, the build context's internal
pluginData
cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that returnpluginData
objects fromonResolve
and/oronLoad
callbacks.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.22.0
or~0.22.0
. See npm's documentation about semver for more information.Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made
--packages=external
the default behavior with--platform=node
. The default is now back to--packages=bundle
.I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I 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 completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with
--jsx=preserve
. Here is an example:<Foo>
<Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;
Package name: @rollup/rollup-darwin-arm64
4.21.0
2024-08-18
Features
Pull Requests
noConflict
option in REPL. (@ 7086cmd)4.20.0
2024-08-03
Features
Pull Requests
Package name: @rollup/rollup-linux-x64-gnu
4.21.0
2024-08-18
Features
Pull Requests
noConflict
option in REPL. (@ 7086cmd)4.20.0
2024-08-03
Features
Pull Requests
Package name: @tanstack/react-query
Version 5.51.24 - 8/19/24, 11:03 AM
Changes
Refactor
Ci
Docs
Doc
Packages
Version 5.51.23 - 8/8/24, 8:02 AM
Changes
Fix
Docs
Packages
Package name: @tanstack/react-query-devtools
Version 5.51.24 - 8/19/24, 11:03 AM
Changes
Refactor
Ci
Docs
Doc
Packages
Version 5.51.23 - 8/8/24, 8:02 AM
Changes
Fix
Docs
Packages
Package name: @tanstack/react-router
Version 1.48.4 - 8/19/24, 8:45 AM
Changes
Fix
Packages
Version 1.48.1 - 8/15/24, 12:31 AM
Changes
Fix
notFoundMode
and update the RouterOptions JSDoc comments (#2133) (c66e1b5) by Sean CassierePackages
Package name: @tanstack/react-virtual
Version 3.10.1 - 8/20/24, 3:57 AM
Changes
Fix
Packages
fix: sync versions with published already (#803)
Version 3.9.0 - 8/14/24, 12:20 PM
Changes
Feat
Chore
Packages
Package name: @tanstack/router-devtools
Version 1.48.4 - 8/19/24, 8:45 AM
Changes
Fix
Packages
Version 1.48.1 - 8/15/24, 12:31 AM
Changes
Fix
notFoundMode
and update the RouterOptions JSDoc comments (#2133) (c66e1b5) by Sean CassierePackages
Important
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: