-
Notifications
You must be signed in to change notification settings - Fork 1
chore(deps): update non-major #162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
e7e13c0 to
74ebd71
Compare
74ebd71 to
747cf72
Compare
747cf72 to
d7826b1
Compare
d7826b1 to
bd19ef5
Compare
bd19ef5 to
9f5c2f4
Compare
9f5c2f4 to
1d0d3b1
Compare
1d0d3b1 to
cd05ecd
Compare
cd05ecd to
54fbfcc
Compare
54fbfcc to
7157d7b
Compare
7157d7b to
1b6ac4c
Compare
1b6ac4c to
dfa83ae
Compare
dfa83ae to
38ea6bf
Compare
ea03336 to
4a0d62f
Compare
4a0d62f to
e7bfa28
Compare
e7bfa28 to
67e2695
Compare
67e2695 to
9145538
Compare
9145538 to
a8b476e
Compare
a8b476e to
79b81f5
Compare
79b81f5 to
31fe3f8
Compare
31fe3f8 to
e0124e6
Compare
e0124e6 to
8c55339
Compare
8c55339 to
2ae6096
Compare
2ae6096 to
eb22852
Compare
eb22852 to
d78dda3
Compare
d78dda3 to
81ee7fa
Compare
81ee7fa to
ae13f2c
Compare
This PR contains the following updates:
^7.28.4→^7.29.0^7.28.3→^7.29.0^7.27.1→^7.28.5^7.27.1→^7.28.5^4.7.0→^4.7.1^8.1.21→^8.1.29^2.0.1→^2.0.3^2.0.0→^2.1.0^3.1.10→^3.1.11^16.3.0→^16.3.2^22.18.10→^22.19.10^19.2.7→^19.2.13^1.17.4→^1.18.0^0.25.11→^0.27.3^2.2.3→^2.3.4^1.31.0→^1.43.0^3.6.2→^3.8.1^19.2.1→^19.2.4^19.2.1→^19.2.4^19.2.1→^19.2.4Release Notes
babel/babel (@babel/core)
v7.29.0Compare Source
v7.29.0 (2026-01-31)
Thanks @simbahax for your first PR!
🚀 New Feature
babel-typesbabel-standalone🐛 Bug Fix
babel-parserextendsclause (@nicolo-ribaudo)babel-traversebabel-plugin-transform-block-scoping,babel-traverse🏃♀️ Performance
babel-generator,babel-runtime-corejs3Committers: 6
v7.28.6Compare Source
v7.28.5Compare Source
👓 Spec Compliance
babel-parserRuntime Errors for Function Call Assignment Targets(@liuxingbaoyu)babel-helper-validator-identifier🐛 Bug Fix
babel-plugin-proposal-destructuring-privatebabel-parser@babel/parsererror typing (@JLHwung)babel-plugin-proposal-discard-binding,babel-plugin-transform-destructuringrestcorrectly returns plain array (@liuxingbaoyu)babel-helper-create-class-features-plugin,babel-helper-member-expression-to-functions,babel-plugin-transform-block-scoping,babel-plugin-transform-optional-chaining,babel-traverse,babel-typesJSXIdentifierhandling inisReferencedIdentifier(@JLHwung)babel-traverse🏠 Internal
babel-types🏃♀️ Performance
babel-corebuildCodeFrameError(@liuxingbaoyu)babel/babel (@babel/preset-react)
v7.28.5Compare Source
👓 Spec Compliance
babel-parserRuntime Errors for Function Call Assignment Targets(@liuxingbaoyu)babel-helper-validator-identifier🐛 Bug Fix
babel-plugin-proposal-destructuring-privatebabel-parser@babel/parsererror typing (@JLHwung)babel-plugin-proposal-discard-binding,babel-plugin-transform-destructuringrestcorrectly returns plain array (@liuxingbaoyu)babel-helper-create-class-features-plugin,babel-helper-member-expression-to-functions,babel-plugin-transform-block-scoping,babel-plugin-transform-optional-chaining,babel-traverse,babel-typesJSXIdentifierhandling inisReferencedIdentifier(@JLHwung)babel-traverse🏠 Internal
babel-types🏃♀️ Performance
babel-corebuildCodeFrameError(@liuxingbaoyu)ianvs/prettier-plugin-sort-imports (@ianvs/prettier-plugin-sort-imports)
v4.7.1Compare Source
What's Changed
Fixes
Dependencies
Docs
New Contributors
Full Changelog: IanVS/prettier-plugin-sort-imports@v4.7.0...v4.7.1
sanity-io/pkg-utils (@sanity/pkg-utils)
v8.1.29Compare Source
Bug Fixes
v8.1.28Compare Source
Bug Fixes
v8.1.27Compare Source
Bug Fixes
v8.1.26Compare Source
Bug Fixes
v8.1.25Compare Source
Bug Fixes
v8.1.24Compare Source
Bug Fixes
v8.1.23Compare Source
Bug Fixes
v8.1.22Compare Source
Bug Fixes
sanity-io/prettier-config (@sanity/prettier-config)
v2.0.3Compare Source
Bug Fixes
v2.0.2Compare Source
Bug Fixes
sanity-io/pkg-utils (@sanity/tsconfig)
v2.1.0Compare Source
Minor Changes
f8d6dccThanks @stipsan! - AddnoEmitOnError: falsetorecommendedpresetsanity-io/ui (@sanity/ui)
v3.1.11Compare Source
Bug Fixes
framer-motionwithmotion/react(cc49ab6)testing-library/react-testing-library (@testing-library/react)
v16.3.2Compare Source
v16.3.1Compare Source
vanilla-extract-css/vanilla-extract (@vanilla-extract/css)
v1.18.0Compare Source
Minor Changes
#1566
8b49b35Thanks @lfantone! -style: Add support for@starting-stylerulesEXAMPLE USAGE:
Patch Changes
#1646
0b2c09eThanks @plesiecki! - Swap the order ofcreateVar's overloads to enable inference ofVarDelcarationtype#1666
c6047fbThanks @askoufis! - Remove custom container properties typeThe
csstypepackage used by Vanilla Extract now provides types for container properties, so the custom type definitions that were previously necessary have been removed.v1.17.5Compare Source
Patch Changes
11a7c66Thanks @askoufis! - Updatecsstypedependency to^3.2.3evanw/esbuild (esbuild)
v0.27.3Compare Source
Preserve URL fragments in data URLs (#4370)
Consider the following HTML, CSS, and SVG:
index.html:icons.css:triangle.svg:The CSS uses a URL fragment (the
#x) to reference theclipPathelement in the SVG file. Previously esbuild's CSS bundler didn't preserve the URL fragment when bundling the SVG using thedataurlloader, which broke the bundled CSS. With this release, esbuild will now preserve the URL fragment in the bundled CSS:Parse and print CSS
@scoperules (#4322)This release includes dedicated support for parsing
@scoperules in CSS. These rules include optional "start" and "end" selector lists. One important consequence of this is that the local/global status of names in selector lists is now respected, which improves the correctness of esbuild's support for CSS modules. Minification of selectors inside@scoperules has also improved slightly.Here's an example:
Fix a minification bug with lowering of
for await(#4378, #4385)This release fixes a bug where the minifier would incorrectly strip the variable in the automatically-generated
catchclause of loweredfor awaitloops. The code that generated the loop previously failed to mark the internal variable references as used.Update the Go compiler from v1.25.5 to v1.25.7 (#4383, #4388)
This PR was contributed by @MikeWillCook.
v0.27.2Compare Source
Allow import path specifiers starting with
#/(#4361)Previously the specification for
package.jsondisallowed import path specifiers starting with#/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping#/*to./src/*(previously you had to use another character such as#_*instead, which was more confusing). There is some more context in nodejs/node#49182.This change was contributed by @hybrist.
Automatically add the
-webkit-maskprefix (#4357, #4358)This release automatically adds the
-webkit-vendor prefix for themaskCSS shorthand property:This change was contributed by @BPJEnnova.
Additional minification of
switchstatements (#4176, #4359)This release contains additional minification patterns for reducing
switchstatements. Here is an example:Forbid
usingdeclarations insideswitchclauses (#4323)This is a rare change to remove something that was previously possible. The Explicit Resource Management proposal introduced
usingdeclarations. These were previously allowed insidecaseanddefaultclauses inswitchstatements. This had well-defined semantics and was already widely implemented (by V8, SpiderMonkey, TypeScript, esbuild, and others). However, it was considered to be too confusing because of how scope works in switch statements, so it has been removed from the specification. This edge case will now be a syntax error. See tc39/proposal-explicit-resource-management#215 and rbuckton/ecma262#14 for details.Here is an example of code that is no longer allowed:
That code will now have to be modified to look like this instead (note the additional
{and}block statements around each case body):This is not being released in one of esbuild's breaking change releases since this feature hasn't been finalized yet, and esbuild always tracks the current state of the specification (so esbuild's previous behavior was arguably incorrect).
v0.27.1Compare Source
Fix bundler bug with
varnested insideif(#4348)This release fixes a bug with the bundler that happens when importing an ES module using
require(which causes it to be wrapped) and there's a top-levelvarinside anifstatement without being wrapped in a{ ... }block (and a few other conditions). The bundling transform needed to hoist thesevardeclarations outside of the lazy ES module wrapper for correctness. See the issue for details.Fix minifier bug with
forinsidetryinside label (#4351)This fixes an old regression from version v0.21.4. Some code was introduced to move the label inside the
trystatement to address a problem with transforming labeledfor awaitloops to avoid theawait(the transformation involves converting thefor awaitloop into aforloop and wrapping it in atrystatement). However, it introduces problems for cross-compiled JVM code that uses all three of these features heavily. This release restricts this transform to only apply toforloops that esbuild itself generates internally as part of thefor awaittransform. Here is an example of some affected code:Inline IIFEs containing a single expression (#4354)
Previously inlining of IIFEs (immediately-invoked function expressions) only worked if the body contained a single
returnstatement. Now it should also work if the body contains a single expression statement instead:The minifier now strips empty
finallyclauses (#4353)This improvement means that
finallyclauses containing dead code can potentially cause the associatedtrystatement to be removed from the output entirely in minified builds:Allow tree-shaking of the
SymbolconstructorWith this release, calling
Symbolis now considered to be side-effect free when the argument is known to be a primitive value. This means esbuild can now tree-shake module-level symbol variables:v0.27.0Compare 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
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.26.0or~0.26.0. See npm's documentation about semver for more information.Use
Uint8Array.fromBase64if available (#4286)With this release, esbuild's
binaryloader will now use the newUint8Array.fromBase64function unless it's unavailable in the configured target environment. If it's unavailable, esbuild's previous code for this will be used as a fallback. Note that this means you may now need to specifytargetwhen using this feature with Node (for example--target=node22) unless you're using Node v25+.Update the Go compiler from v1.23.12 to v1.25.4 (#4208, #4311)
This raises the operating system requirements for running esbuild:
v0.26.0Compare Source
Enable trusted publishing (#4281)
GitHub and npm are recommending that maintainers for packages such as esbuild switch to trusted publishing. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.
Unfortunately there isn't really a way to test that this works other than to do it live. So this release is that live test. Hopefully this release is uneventful and is exactly the same as the previous one (well, except for the green provenance attestation checkmark on npm that happens with trusted publishing).
v0.25.12Compare Source
Fix a minification regression with CSS media queries (#4315)
The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for
@media <media-type> and <media-condition-without-or> { ... }was missing an equality check for the<media-condition-without-or>part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression.Update the list of known JavaScript globals (#4310)
This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global
Arrayproperty is considered to be side-effect free but accessing the globalscrollYproperty can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties:From ES2017:
AtomicsSharedArrayBufferFrom ES2020:
BigInt64ArrayBigUint64ArrayFrom ES2021:
FinalizationRegistryWeakRefFrom ES2025:
Float16ArrayIteratorNote that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from
Iterator:Add support for the new
@view-transitionCSS rule (#4313)With this release, esbuild now has improved support for pretty-printing and minifying the new
@view-transitionrule (which esbuild was previously unaware of):The new view transition feature provides a mechanism for creating animated transitions between documents in a multi-page app. You can read more about view transition rules here.
This change was contributed by @yisibl.
Trim CSS rules that will never match
The CSS minifier will now remove rules whose selectors contain
:is()and:where()as those selectors will never match. These selectors can currently be automatically generated by esbuild when you give esbuild nonsensical input such as the following:This input is nonsensical because CSS nesting is (unfortunately) not supported inside of pseudo-elements such as
:before. Currently esbuild generates a rule containing:is()in this case when you tell esbuild to transform nested CSS into non-nested CSS. I think it's reasonable to do that as it sort of helps explain what's going on (or at least indicates that something is wrong in the output). It shouldn't be present in minified code, however, so this release now strips it out.ilearnio/module-alias (module-alias)
v2.3.4Compare Source
v2.3.3Compare Source
v2.3.2Compare Source
v2.3.1Compare Source
v2.3.0Compare Source
oxc-project/oxc (oxlint)
v1.43.0Compare Source
v1.42.0Compare Source
🚀 Features
15d69dclinter: Implement react/display-name rule (#18426) (camchenry)📚 Documentation
8ccd853npm: Update package homepage URLs and add keywords (#18509) (Boshen)v1.41.0Compare Source
📚 Documentation
8a294d5oxfmt, oxlint: Update logo (#18242) (Dunqing)v1.40.0Compare Source
v1.39.0Compare Source
v1.38.0Compare Source
v1.37.0Compare Source
💥 BREAKING CHANGES
f7da875oxlint: [BREAKING] Remove oxc_language_server binary (#17457) (Boshen)📚 Documentation
7e5fc90linter: Update list of plugins that are reserved. (#17516) (connorshea)v1.36.0Compare Source
v1.35.0Compare Source
🚀 Features
9e624c9linter/react: AddversiontoReactPluginSettings(#17169) (camc314)v1.34.0Compare Source
🚀 Features
a0f74a0linter/config: Allow aliasing plugin names to allow names the same as builtin plugins (#15569) (Cameron)🐛 Bug Fixes
005ec25linter: Permit$schema.oxlintrc.jsonstruct (#17060) (Copilot)d446c43linter: Prevent extra fields from being present on oxlint config file (#16874) (connorshea)v1.33.0Compare Source
v1.32.0Compare Source
prettier/prettier (prettier)
v3.8.1Compare Source
v3.8.0Compare Source
diff
🔗 Release note
v3.7.4Compare Source
diff
LWC: Avoid quote around interpolations (#18383 by @kovsu)
TypeScript: Fix comment inside union type gets duplicated (#18393 by @fisker)
TypeScript: Fix unstable comment print in union type comments (#18395 by @fisker)