chore(deps): update all non-major dependencies #934
Merged
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.
This PR contains the following updates:
^2.27.5
->^2.27.7
^9.5.0
->^9.6.0
^2.2.2
->^2.3.0
^2.5.17
->^2.5.18
^20.14.6
->^20.14.10
^12.9.0
->^12.10.0
^0.4.7
->^0.5.1
^0.21.5
->^0.23.0
^9.5.0
->^9.6.0
^2.40.0
->^2.41.0
^15.6.0
->^15.8.0
^6.2.0
->^6.2.2
~1.44.1
->~1.45.1
9.4.0
->9.5.0
^8.4.38
->^8.4.39
^5.0.0-next.160
->^5.0.0-next.178
^3.8.1
->^3.8.4
^0.39.1
->^0.39.2
^5.4.5
->^5.5.3
^8.0.0-alpha.30
->^8.0.0-alpha.41
^5.3.1
->^5.3.3
Release Notes
changesets/changesets (@changesets/cli)
v2.27.7
Compare Source
Patch Changes
#1047
d108fa6
Thanks @patzick! - Fixed a crash that could occur when depending on a tagged version of another workspace package.#1400
dd6e5bb
Thanks @Andarist! - Fixed a crash that prevented the CLI from running in a scenario when a workspace depends on the root workspaceUpdated dependencies [
d108fa6
,dd6e5bb
,dd6e5bb
]:v2.27.6
Compare Source
Patch Changes
#1392
f295b3e
Thanks @bluwy! - Replacemeow
dependency withmri
to reduce the number of transitive dependencies#1390
6a3452e
Thanks @bluwy! - Displaychangeset status --verbose
in list form and removetty-table
dependencyeslint/eslint (@eslint/js)
v9.6.0
Compare Source
eslint-stylistic/eslint-stylistic (@stylistic/eslint-plugin-js)
v2.3.0
Compare Source
Features
object-curly-newline
andobject-property-newline
(#444) (036d3de)Bug Fixes
jsx-indent
rule in favor ofindent
(#447) (57dd2e8)sveltejs/kit (@sveltejs/kit)
v2.5.18
Compare Source
Patch Changes
fix: respect HTML attributes
enctype
andformenctype
for forms withuse:enhance
(#12198)fix: prevent client import error when a
hooks.server
file imports a private environment variable (#12195)fix: set default
Content-Type
header toapplication/x-www-form-urlencoded
forPOST
form submissions withuse:enhance
to align with native form behaviour (#12198)carbon-design-system/carbon-icons-svelte (carbon-icons-svelte)
v12.10.0
Compare Source
Features
@carbon/icons
to v11.44.1 (net +2 icons)Rich-Harris/dts-buddy (dts-buddy)
v0.5.1
Compare Source
v0.5.0
Compare Source
evanw/esbuild (esbuild)
v0.23.0
Compare Source
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:v0.22.0
Compare Source
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.21.0
or~0.21.0
. See npm's documentation about semver for more information.Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for
--platform=node
) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use--packages=external
to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.With this release, esbuild will now omit packages from the bundle by default when the platform is
node
(i.e. the previous behavior of--packages=external
is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do--packages=bundle
to allow packages to be included in the bundle (i.e. the previous default behavior). Note that--packages=bundle
doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using--external:
even when--packages=bundle
is present.The
--packages=
setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of/
or.
or..
are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a#
character) and TypeScript path remappings viapaths
and/orbaseUrl
intsconfig.json
(which are applied first).Drop support for older platforms (#3802)
This release drops support for the following operating systems:
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.
Note that this only affects the binary esbuild executables that are published to the
esbuild
npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the
esbuild-wasm
package and versions of node before node 17.4 (specifically thecrypto.getRandomValues
function).Update
await using
behavior to match TypeScriptTypeScript 5.5 subtly changes the way
await using
behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.Allow
es2024
as a target environmentThe ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression
/v
flag. With--target=es2024
, regular expressions that use the/v
flag will now be passed through untransformed instead of being transformed into a call tonew RegExp
.Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)
With this release, you should now be able to install the
esbuild
npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.This was contributed by @ikmckenz.
Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)
The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a
.wasm
file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.
This release publishes esbuild precompiled for WASI preview 1 to the
@esbuild/wasi-preview1
package on npm (specifically the file@esbuild/wasi-preview1/esbuild.wasm
). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.Warn about
onResolve
plugins not setting a path (#3790)Plugins that return values from
onResolve
without resolving the path (i.e. without setting eitherpath
orexternal: true
) will now cause a warning. This is because esbuild only uses return values fromonResolve
if it successfully resolves the path, and it's not good for invalid input to be silently ignored.Add a new Go API for running the CLI with plugins (#3539)
With esbuild's Go API, you can now call
cli.RunWithPlugins(args, plugins)
to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.This was contributed by @edewit.
eslint/eslint (eslint)
v9.6.0
Compare Source
sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)
v2.41.0
Compare Source
Minor Changes
be64d36
Thanks @ota-meshi! - fix: broken indentation of if condition insvelte/indent
rulePatch Changes
#789
0bc17df
Thanks @KuSh! - chore: Use eslint types for exported configs#805
6e4d3ed
Thanks @baseballyama! - fix: updatesvelte-eslint-parser
to fix nested{#snippet}
#800
580f44f
Thanks @ota-meshi! - feat: add name to flat configs.sindresorhus/globals (globals)
v15.8.0
Compare Source
v15.7.0
Compare Source
f017b0f
bcomnes/npm-run-all2 (npm-run-all2)
v6.2.2
Compare Source
Commits
fc35f0d
v6.2.1
Compare Source
Merged
#143
#142
#141
#138
microsoft/playwright (playwright-core)
v1.45.1
Compare Source
v1.45.0
Compare Source
pnpm/pnpm (pnpm)
v9.5.0
Compare Source
postcss/postcss (postcss)
v8.4.39
Compare Source
CssSyntaxError
types (by @romainmenke).sveltejs/svelte (svelte)
v5.0.0-next.178
Compare Source
Patch Changes
v5.0.0-next.177
Compare Source
Patch Changes
breaking: play transitions on
mount
by default (#12351)fix: make
<select>
<option value>
behavior consistent (#12316)chore: stricter control flow syntax validation in runes mode (#12342)
fix: resolve legacy component props equality for mutations (#12348)
fix: make
$state
component exports settable (#12345)v5.0.0-next.176
Compare Source
Patch Changes
fix: correct start of
{:else if}
and{:else}
(#12043)fix: reverse parent/child order in invalid HTML warning (#12336)
fix: reorder reactive statements during migration (#12329)
feat: better
<svelte:element>
SSR output (#12339)chore: align warning and error objects, add frame property (#12326)
fix: ensure
$effect.root
is ignored on the server (#12332)fix: enable local transitions on
svelte:element
(#12346)v5.0.0-next.175
Compare Source
Patch Changes
fix: correctly compile $effect.root in svelte modules (#12315)
fix: ensure
bind:this
works with component with no return value (#12290)v5.0.0-next.174
Compare Source
Patch Changes
fix: bail out of event hoisting when referencing store subscriptions (#12301)
chore: make store initialization logic simpler (#12281)
fix: make props optional during SSR (#12284)
fix: ensure each blocks properly handle $state.frozen objects in prod (#12305)
fix: ensure rest props access on hoisted event handlers works (#12298)
fix: lazily create a derived for each read method on
SvelteDate.prototype
(#12110)v5.0.0-next.173
Compare Source
Patch Changes
v5.0.0-next.172
Compare Source
Patch Changes
v5.0.0-next.171
Compare Source
Patch Changes
v5.0.0-next.170
Compare Source
Patch Changes
fix: bump dts-buddy for better type generation (#12262)
breaking: expose
CompileError
interface, not class (#12255)v5.0.0-next.169
Compare Source
Patch Changes
breaking: rename
svelte/reactivity
helpers to includeSvelte
prefix (#12248)fix: avoid duplicate signal dependencies (#12245)
v5.0.0-next.168
Compare Source
Patch Changes
fix: ensure HMR doesn't mess with anchor nodes (#12242)
fix: deconflict multiple snippets of the same name (#12221)
v5.0.0-next.167
Compare Source
Patch Changes
fix: make more types from
svelte/compiler
public (#12189)fix: support contenteditable binding undefined fallback (#12210)
breaking: prevent usage of arguments keyword in certain places (#12191)
fix(types): export CompileResult and Warning (#12212)
fix: ensure element dir properties persist with text changes (#12204)
fix: disallow accessing internal Svelte props (#12207)
fix: make media bindings more robust (#12206)
fix: allow slot attribute inside snippets (#12188)
feat: allow
let props = $props()
and optimize prop read access (#12201)feat: improve type arguments for Snippet and $bindable (#12197)
v5.0.0-next.166
Compare Source
Patch Changes
fix: remove correct event listener from document (#12101)
fix: correctly serialize object assignment expressions (#12175)
fix: robustify migration script around indentation and comments (#12176)
fix: improve await block behaviour in non-runes mode (#12179)
fix: improve select handling of dynamic value with placeholders (#12181)
v5.0.0-next.165
Compare Source
Patch Changes
breaking: bump dts-buddy (#12134)
fix: throw compilation error for malformed snippets (#12144)
v5.0.0-next.164
Compare Source
Patch Changes
fix: prevent
a11y_label_has_associated_control
false positive for component or render tag in<label>
(#12119)fix: allow multiple optional parameters with defaults in snippets (#12070)
v5.0.0-next.163
Patch Changes
feat: more accurate
render
/mount
/hydrate
options (#12111)fix: better binding interop between runes/non-runes components (#12123)
v5.0.0-next.162
Patch Changes
sveltejs/language-tools (svelte-check)
v3.8.4
Compare Source
v3.8.3
Compare Source
v3.8.2
Compare Source
sveltejs/svelte-eslint-parser (svelte-eslint-parser)
v0.39.2
Compare Source
Patch Changes
48a7001
Thanks @ota-meshi! - fix: parsing error for nesting{#snippet}
Microsoft/TypeScript (typescript)
v5.5.3
Compare Source
v5.5.2
Compare Source
typescript-eslint/typescript-eslint (typescript-eslint)
v8.0.0-alpha.41
Compare Source
v8.0.0-alpha.39
Compare Source
v8.0.0-alpha.38
Compare Source
v8.0.0-alpha.37
Compare Source
v8.0.0-alpha.36
Compare Source
v8.0.0-alpha.35
Compare Source
v8.0.0-alpha.34
Compare Source
v8.0.0-alpha.33
Compare Source
v8.0.0-alpha.32
Compare Source
v8.0.0-alpha.31
Compare Source
vitejs/vite (vite)
v5.3.3
Compare Source
v5.3.2
Compare Source
location
(#17528) (a8e2f6f), closes #17528Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.