chore(deps): update all non-major dependencies #102
+844
−942
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:
19.2.1
->19.3.0
19.1.0
->19.2.2
^1.7.19
->^1.7.22
^1.9.1
->^1.11.2
^3.7.1
->^3.8.0
4.3.14
->4.3.16
20.12.3
->20.14.2
8.0.2
->8.1.0
0.58.9
->0.60.4
5.0.4
->5.0.5
^10.9.0
->^10.10.0
5.1.0
->5.1.1
^4.3.2
->^4.3.3
0.20.2
->0.21.4
15.0.0
->15.3.0
^4.2.1
->^4.4.4
15.2.2
->15.2.5
3.2.5
->3.3.1
1.72.0
->1.77.4
7.6.0
->7.6.2
12.3.0
->12.3.2
^0.8.3
->^0.9.0
4.7.1
->4.12.0
5.4.3
->5.4.5
0.58.9
->0.60.4
5.2.8
->5.2.12
3.4.21
->3.4.27
^4.3.0
->^4.3.2
2.0.7
->2.0.19
3.44.0
->3.59.0
^3.22.4
->^3.23.8
Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v19.3.0
Compare Source
Note: Version bump only for package @commitlint/cli
19.2.2 (2024-04-14)
Note: Version bump only for package @commitlint/cli
19.2.1 (2024-03-19)
Note: Version bump only for package @commitlint/cli
v19.2.2
Compare Source
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v19.2.2
Compare Source
Note: Version bump only for package @commitlint/config-conventional
unocss/unocss (@unocss/reset)
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
v0.59.4
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.59.3
Compare Source
🐞 Bug Fixes
borderRadius
from theme to autosuggestrounded
values - by @DamianOsipiuk in https://github.com/unocss/unocss/issues/3727 (18346)View changes on GitHub
v0.59.2
Compare Source
🐞 Bug Fixes
@unocss/webpack
to ESM First - by @userquin in https://github.com/unocss/unocss/issues/3708 (25e97)View changes on GitHub
v0.59.1
Compare Source
🐞 Bug Fixes
marker
pesudo element - by @Simon-He95 in https://github.com/unocss/unocss/issues/3702 (0b4a9)View changes on GitHub
v0.59.0
Compare Source
vitejs/vite-plugin-vue (@vitejs/plugin-vue)
v5.0.5
__VUE_PROD_DEVTOOLS__
(#81) (277a3ab), closes #81chaijs/chai (chai)
v5.1.1
Compare Source
What's Changed
toThrow
by @43081j in https://github.com/chaijs/chai/pull/1609New Contributors
Full Changelog: chaijs/chai@v5.1.0...v5.1.1
evanw/esbuild (esbuild)
v0.21.4
Compare Source
Update support for import assertions and import attributes in node (#3778)
Import assertions (the
assert
keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with--target=node22
or above:Import attributes (the
with
keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with--target=node18.N
ifN
is 20 or greater.Fix
for await
transform when a label is presentThis release fixes a bug where the
for await
transform, which wraps the loop in atry
statement, previously failed to also move the loop's label into thetry
statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:Do additional constant folding after cross-module enum inlining (#3416, #3425)
This release adds a few more cases where esbuild does constant folding after cross-module enum inlining.
Pass import attributes to on-resolve plugins (#3384, #3639, #3646)
With this release, on-resolve plugins will now have access to the import attributes on the import via the
with
property of the arguments object. This mirrors thewith
property of the arguments object that's already passed to on-load plugins. In addition, you can now passwith
to theresolve()
API call which will then forward that value on to all relevant plugins. Here's an example of a plugin that can now be written:Formatting support for the
@position-try
rule (#3773)Chrome shipped this new CSS at-rule in version 125 as part of the CSS anchor positioning API. With this release, esbuild now knows to expect a declaration list inside of the
@position-try
body block and will format it appropriately.Always allow internal string import and export aliases (#3343)
Import and export names can be string literals in ES2022+. Previously esbuild forbid any usage of these aliases when the target was below ES2022. Starting with this release, esbuild will only forbid such usage when the alias would otherwise end up in output as a string literal. String literal aliases that are only used internally in the bundle and are "compiled away" are no longer errors. This makes it possible to use string literal aliases with esbuild's
inject
feature even when the target is earlier than ES2022.v0.21.3
Compare Source
Implement the decorator metadata proposal (#3760)
This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:
This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
Fix bundled decorators in derived classes (#3768)
In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:
Fix
tsconfig.json
files inside symlinked directories (#3767)This release fixes an issue with a scenario involving a
tsconfig.json
file thatextends
another file from within a symlinked directory that uses thepaths
feature. In that case, the implicitbaseURL
value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done fortsconfig.json
because it's special-cased (the regular path resolver can't be used because the information insidetsconfig.json
is involved in path resolution). Note that this fix no longer applies if the--preserve-symlinks
setting is enabled.v0.21.2
Compare Source
Correct
this
in field and accessor decorators (#3761)This release changes the value of
this
in initializers for class field and accessor decorators from the module-levelthis
value to the appropriatethis
value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:Allow
es2023
as a target environment (#3762)TypeScript recently added
es2023
as a compilation target, so esbuild now supports this too. There is no difference between a target ofes2022
andes2023
as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.v0.21.1
Compare Source
Fix a regression with
--keep-names
(#3756)The previous release introduced a regression with the
--keep-names
setting and object literals withget
/set
accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:v0.21.0
Compare Source
This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.
Implement the JavaScript decorators proposal (#104)
With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:
Note that this feature is different than the existing "TypeScript experimental decorators" fe
Configuration
📅 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 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.