useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @Conaclos
Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @ematipico
The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @Sec-ant
Enhancements
Enhance tailwind sorting lint rule #1274 with variant support.
Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order.
Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class.
Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight).
Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant.
Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.
useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @Conaclos
Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @ematipico
The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @Sec-ant
Enhancements
Enhance tailwind sorting lint rule #1274 with variant support.
Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order.
Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class.
Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight).
Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant.
Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.
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 your package.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.
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 via paths and/or baseUrl in tsconfig.json (which are applied first).
This release drops support for the following operating systems:
Windows 7
Windows 8
Windows Server 2008
Windows Server 2012
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:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version
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 the crypto.getRandomValues function).
Update await using behavior to match TypeScript
TypeScript 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 environment
The 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 to new 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.
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).
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 your package.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.
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 via paths and/or baseUrl in tsconfig.json (which are applied first).
This release drops support for the following operating systems:
Windows 7
Windows 8
Windows Server 2008
Windows Server 2012
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:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version
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 the crypto.getRandomValues function).
Update await using behavior to match TypeScript
TypeScript 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 environment
The 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 to new 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.
Bumps the dev-dependencies group with 15 updates in the / directory:
1.7.01.8.313.7.313.13.00.20.20.22.07.6.07.6.216.3.116.6.14.7.24.16.05.4.55.5.34.2.14.3.118.2.018.3.118.2.7918.3.318.2.018.3.118.2.2518.3.05.2.85.3.218.2.018.3.124.0.024.1.0Updates
@biomejs/biomefrom 1.7.0 to 1.8.3Release notes
Sourced from
@biomejs/biome's releases.... (truncated)
Changelog
Sourced from
@biomejs/biome's changelog.... (truncated)
Commits
c28d597release: v1.8.3 (#3302)f88b7b2chore: update codegen to include GraphQL (#3301)6f9c938feat(noExportedImports): add lint rule (#3097)cd3bb04chore(deps): update@biomejspackages (#3266)54b4c9arelease: v1.8.2 (#3243)6f8cab7feat(biome_css_analyzer): implement function-linear-gradient-no-nonstandard-d...0d9b60afeat(lint/useValidAutocomplete): add rule (#3143)9d518d8chore(deps): update@biomejspackages (#3145)4a7baaafeat(biome_js_analyzer):noSubstr(#3125)535acc7fix(ci): rule check error messages (#3158)Updates
cypressfrom 13.7.3 to 13.13.0Release notes
Sourced from cypress's releases.
Commits
a16edd5chore: move frontend-shared from a dev dependency to a runtime dependency in ...10f90f9chore: release 13.13.0 (#29781)c0f2f1achore: Update v8 snapshot cache (#29773)aa8aaa1chore: fix testing kitchen sink job against staging as it needs node 20.8 or ...c2473c0dependency: update dependency launch-editor to v2.8.0 (#29770)f2554f1feat: add Angular Signals CT Harness for Angular 17.2 and up for users to be ...ed85a2cchore: Update v8 snapshot cache (#29758)a3f7a3cchore: Update Chrome (beta) to 127.0.6533.26 (#29760)606a43brefactor: CriClient -> traditional class + async factory (#29676)db6afb1dependency: update dependency memfs to v3.5.3 (#29746)Updates
esbuildfrom 0.20.2 to 0.22.0Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
80c6e6epublish 0.22.0 to npm196dcadfix #1874: node defaults to--packages=external3f57db8release notes for #353991663dbProvide API to create a custom esbuild CLI with plugins (#3539)e01c0e0also mention #3665 in release notes65711b3release notes for #367463eb814Add OpenBSD arm64 (#3674)b722000fix #3300, fix #3779: add@esbuild/wasi-preview16679ec8fix: verbose analyse output improperly trimmed (#3785)94f09eafix #3790: warn about incorrectonResolvepluginUpdates
semverfrom 7.6.0 to 7.6.2Release notes
Sourced from semver's releases.
Changelog
Sourced from semver's changelog.
Commits
eb1380bchore: release 7.6.2 (#714)6466ba9fix(lru): use map.delete() directly (#713)d777418chore: release 7.6.1 (#706)988a8dedeps: uninstalllru-cache(#709)5feeb7fchore: postinstall for dependabot template-oss PRdd09b60chore: bump@npmcli/template-ossto 4.22.0c570a34fix(linting): no-unused-varsad8ff11fix: use internal cache implementation3fabe4ddeps: remove lru-cacheec49cdcchore: chore: chore: postinstall for dependabot template-oss PRUpdates
stylelintfrom 16.3.1 to 16.6.1Release notes
Sourced from stylelint's releases.
Changelog
Sourced from stylelint's changelog.
Commits
d902c0b16.6.142d08bdPrepare 16.6.1 (#7721)b4f74e5Ignoretmp/from Prettier (#7726)62b58bcFixno-descending-specificityfalse positives for nested selectors (#7724)72ec18aRefactor to use shared constant fordisabledRangesobject (#7722)b85be3cFix typo in rules.md (#7717)9478c71Bump file-entry-cache from 8.0.0 to 9.0.0 (#7720)211908bFixselector-type-no-unknownfalse positive formodel(#7718)fa85a70Bump lint-staged from 15.2.4 to 15.2.5 (#7719)44de825Bump lint-staged from 15.2.2 to 15.2.4 (#7713)Updates
tsxfrom 4.7.2 to 4.16.0Release notes
Sourced from tsx's releases.
... (truncated)
Commits
da3bcb0chore: upgrade deps3e1e546feat(cjs): improve compatibility with other loadersSuperseded by #987.