-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
chore(deps): update all minor dependencies (minor) #5479
Conversation
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #5479 +/- ##
==========================================
- Coverage 5.73% 5.72% -0.01%
==========================================
Files 278 278
Lines 41999 42013 +14
Branches 490 490
==========================================
- Hits 2409 2407 -2
- Misses 39590 39606 +16
Flags with carried forward coverage won't be shown. Click here to find out more. |
d0e5599
to
92330db
Compare
f8eaaf7
to
e0bfece
Compare
8b693ba
to
682ee6e
Compare
3def21a
to
95ad0ed
Compare
aff0367
to
1c99982
Compare
039a1b5
to
b50c13f
Compare
68d51f3
to
f812e15
Compare
3ee14ad
to
d2e1587
Compare
cab8764
to
a392e20
Compare
|
This PR contains the following updates:
20.14.14
->20.16.1
^0.59.0
->^0.62.0
^0.4.0
->^0.5.0
8.13.1
->8.14.2
13.7.3
->13.13.3
^0.21.5
->^0.23.0
6.5.2
->6.6.0
3.0.0
->3.1.3
3.0.3
->3.1.1
v1.9.3
->v1.10.0
20.12.2
->20.17.0
20.12.2-alpine3.19
->20.17.0-alpine3.19
9.7.1+sha512.faf344af2d6ca65c4c5c8c2224ea77a81a5e8859cbc4e06b1511ddce2f0151512431dd19e6aff31f2c6a8f5f2aced9bd2273e1fed7dd4de1868984059d2c4247
->9.8.0
4.16.5
->4.17.0
4.23.0
->4.25.0
^0.25.12
->^0.26.0
~5.4.3
->~5.5.0
~5.4.5
->~5.5.0
^0.59.0
->^0.62.0
^0.26.0
->^0.27.0
5.3.5
->5.4.2
^0.19.7
->^0.20.0
1.1.4
->1.3.3
Release Notes
unocss/unocss (@unocss/reset)
v0.62.2
Compare Source
🚀 Features
DEFAULT
key of theme - by @zyyv in https://github.com/unocss/unocss/issues/4072 (3f010)🐞 Bug Fixes
View changes on GitHub
v0.62.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.62.0
Compare Source
🚀 Features
@typescript-eslint
- by @antfu (aaf3a)content
option in presets - by @Jannchie and Anthony Fu in https://github.com/unocss/unocss/issues/4041 (2466d)🐞 Bug Fixes
View changes on GitHub
v0.61.9
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.61.8
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.61.7
Compare Source
🚀 Features
autocomplete.strict
config - by @Simon-He95 and @antfu in https://github.com/unocss/unocss/issues/3957 (77db3)🐞 Bug Fixes
unconfig
, fix #3812 - by @antfu and userquin in https://github.com/unocss/unocss/issues/3814 and https://github.com/unocss/unocss/issues/3812 (100d8)mini
andwind
- by @MellowCo and @antfu in https://github.com/unocss/unocss/issues/4025 (870d3)View changes on GitHub
v0.61.6
Compare Source
🚀 Features
(float - by **end)
(#3997)** and Anthony Fu (clear)-(start)🐞 Bug Fixes
View changes on GitHub
v0.61.5
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.61.4
Compare Source
🚀 Features
createRecoveryConfigLoader
- by @Simon-He95, @antfu and Anthony Fu in https://github.com/unocss/unocss/issues/3953 (64fb0)🐞 Bug Fixes
flushTask
- by @KermanX in https://github.com/unocss/unocss/issues/3984 (141cd)local
node10 types - by @userquin in https://github.com/unocss/unocss/issues/3963 (3ff7c)View changes on GitHub
v0.61.3
Compare Source
🚀 Features
View changes on GitHub
v0.61.2
Compare Source
No significant changes
View changes on GitHub
v0.61.0
Compare Source
🚀 Features
🐞 Bug Fixes
transform-cpu
should not includerotate-x
androtate-y
- by @zzc6332 in https://github.com/unocss/unocss/issues/3813 (ae072)View changes on GitHub
v0.60.4
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.60.3
Compare Source
🚀 Features
text-align
utility - by @UltraCakeBakery, Chris and @antfu in https://github.com/unocss/unocss/issues/3796 (5f2a8)🐞 Bug Fixes
unocss:global:build:bundle
has no CSS placeholder - by @Simon-He95 in https://github.com/unocss/unocss/issues/3802 (210a2)🏎 Performance
resolveBreakpoints
- by @antfu (05d90)View changes on GitHub
v0.60.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.60.1
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.60.0
Compare Source
🚨 Breaking Changes
.default
suffix from d.ts and d.cts files - by @userquin in https://github.com/unocss/unocss/issues/3750 (e9f5b)🚀 Features
🐞 Bug Fixes
selection
- by @zyyv in https://github.com/unocss/unocss/issues/3771 (18df5)View changes on GitHub
vite-pwa/vitepress (@vite-pwa/vitepress)
v0.5.0
Compare Source
🚨 Breaking Changes
View changes on GitHub
streetsidesoftware/cspell (cspell)
v8.14.2
Compare Source
v8.14.1
Compare Source
v8.13.3
Compare Source
v8.13.2
Compare Source
evanw/esbuild (esbuild)
v0.23.1
Compare Source
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: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.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 ofConfiguration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.