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
base: develop
Are you sure you want to change the base?
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 failed.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #5479 +/- ##
=========================================
Coverage ? 5.72%
=========================================
Files ? 278
Lines ? 42013
Branches ? 490
=========================================
Hits ? 2407
Misses ? 39606
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. |
d0e5599
to
92330db
Compare
4cda471
to
f8eaaf7
Compare
f8eaaf7
to
e0bfece
Compare
This PR contains the following updates:
3.43.1
->3.44.1
8.7.0
->8.8.0
7.6.0
->7.8.0
7.6.0
->7.8.0
^0.4.0
->^0.5.0
1.5.3
->1.6.0
1.5.3
->1.6.0
1.5.3
->1.6.0
3.21.2
->3.23.0
8.12.0
->8.13.0
8.7.0
->8.8.0
13.7.3
->13.8.1
13.7.3
->13.8.1
3.28.1
->3.29.2
^0.20.2
->^0.21.0
v1.9.3
->v1.10.0
20.12.2
->20.13.0
20.12.2-alpine3.19
->20.13.0-alpine3.19
4.7.3
->4.9.3
4.15.0
->4.18.2
^0.26.0
->^0.27.0
^0.19.7
->^0.20.0
1.5.3
->1.6.0
7.0.0
->7.1.0
Release Notes
streetsidesoftware/cspell (@cspell/eslint-plugin)
v8.8.0
Compare Source
Note: Version bump only for package @cspell/eslint-plugin
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.8.0
Compare Source
🩹 Fixes
eslint-plugin: [no-unsafe-argument] handle tagged templates
eslint-plugin: [prefer-optional-chain] suggests optional chaining during strict null equality check
eslint-plugin: [consistent-type-assertions] handle tagged templates
eslint-plugin: [no-unsafe-return] handle union types
eslint-plugin: [no-unused-vars] clear error report range
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.7.1
Compare Source
🩹 Fixes
eslint-plugin: [no-unsafe-assignment] handle shorthand property assignment
eslint-plugin: [explicit-function-return-type] fix checking wrong ancestor's return type
eslint-plugin: [prefer-optional-chain] only look at left operand for
requireNullish
eslint-plugin: [no-for-in-array] refine report location
eslint-plugin: [no-unnecessary-type-assertion] allow non-null assertion for void type
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.7.0
Compare Source
🚀 Features
no-new-symbol
withno-new-native-nonconstructor
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.8.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.7.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.7.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
vite-pwa/vitepress (@vite-pwa/vitepress)
v0.5.0
Compare Source
🚨 Breaking Changes
View changes on GitHub
vitest-dev/vitest (@vitest/coverage-v8)
v1.6.0
Compare Source
🚀 Features
includeConsoleOutput
andaddFileAttribute
in junit - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5659 (2f913)🐞 Bug Fixes
resolveId('vitest')
afterbuildStart
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5646 (f5faf)toJSON
for error serialization - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5526 (19a21)*.test-d.*
by default - by @MindfulPol in https://github.com/vitest-dev/vitest/issues/5634 (bfe8a)vite-node
's wrapper only to executed files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5642 (c9883)🏎 Performance
View changes on GitHub
mermaid-js/zenuml-core (@zenuml/core)
v3.23.0
Compare Source
v3.22.1
Compare Source
v3.22.0
Compare Source
ajv-validator/ajv (ajv)
v8.13.0
Compare Source
streetsidesoftware/cspell (cspell)
v8.8.0
Compare Source
Note: Version bump only for package cspell
cypress-io/cypress (cypress)
v13.8.1
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-8-1
v13.8.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-8-0
cytoscape/cytoscape.js (cytoscape)
v3.29.2
Compare Source
Release version v3.29.2
v3.29.1
Compare Source
Release version v3.29.1
v3.29.0
Compare Source
Release version v3.29.0
evanw/esbuild (esbuild)
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" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting
"experimentalDecorators": true
in yourtsconfig.json
file.Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.
This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. 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 decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
Optimize the generated code for private methods
Previously when lowering private methods for old browsers, esbuild would generate one
WeakSet
for each private method. This mirrors similar logic for generating oneWeakSet
for each private field. Using a separateWeakMap
for private fields is necessary as their assignment can be observable:This prints
true false
because this partially-initialized instance has#x
but not#y
. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a singleWeakSet
, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:Fix an obscure bug with lowering class members with computed property keys
When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate
a()
thenb()
thenc()
:Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:
However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an
await
expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into theextends
clause or even before the class itself:Fix some
--keep-names
edge casesThe
NamedEvaluation
syntax-directed operation in the JavaScript specification gives certain anonymous expressions aname
property depending on where they are in the syntax tree. For example, the following initializers convey aname
value:When you enable esbuild's
--keep-names
setting, esbuild generates additional code to represent thisNamedEvaluation
operation so that the value of thename
property persists even when the identifiers are renamed (e.g. due to minification).However, I recently learned that esbuild's implementation of
NamedEvaluation
is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:lycheeverse/lychee-action (lycheeverse/lychee-action)
v1.10.0
Compare Source
What's Changed
actions/checkout
to version4
by @jacobdalamb in https://github.com/lycheeverse/lychee-action/pull/224New Contributors
Full Changelog: lycheeverse/lychee-action@v1.9.3...v1.10.0
nodejs/node (node)
v20.13.0
Compare Source
privatenumber/tsx (tsx)
v4.9.3
Compare Source
Bug Fixes
This release is also available on:
v4.9.2
Compare Source
Bug Fixes
This release is also available on:
v4.9.1
Compare Source
v4.9.0
Compare Source
v4.8.2
Compare Source
Bug Fixes
This release is also available on:
v4.8.1
Compare Source
v4.8.0
Compare Source
sindresorhus/type-fest (type-fest)
v4.18.2
Compare Source
v4.18.1
Compare Source
v4.18.0
Compare Source
New types
Or
909c38e
And
9d628aa
Improvements
TsConfigJson
: Addpreserve
module type andES2022
lib types (#874)7096613
Opaque
: Mark as deprecated (#867)ef7b580
UnwrapOpaque
: Mark as deprecated (#867)ef7b580
v4.17.0
Compare Source
v4.16.0
Compare Source
New types
IsInteger
IsFloat
Fixes
Integer
: Fix handling of some edge-cases (#857)f5b09de
Float
: Fix handling of some edge-cases (#857)f5b09de
unplugin/unplugin-vue-components (unplugin-vue-components)
v0.27.0
Compare Source
🚀 Features
css-in-js
import style - by @JohnsonHuang4396, @antfu, 黄启浩 and JohnsonHuang in https://github.com/unplugin/unplugin-vue-components/issues/703 (5d533)styleExtname
option - by @RSS1102 in https://github.com/unplugin/unplugin-vue-components/issues/740 (c0e66)🐞 Bug Fixes
prettier-ignore
statement so it works - by @HookyGV in https://github.com/unplugin/unplugin-vue-components/issues/729 (e0d37)View changes on GitHub
vite-pwa/vite-plugin-pwa (vite-plugin-pwa)
v0.20.0
Compare Source
🚨 Breaking Changes
View changes on GitHub
googlechrome/workbox (workbox-window)
v7.1.0
Compare Source
What's Changed ✏️
Thanks 🙏
Full Changelog: GoogleChrome/workbox@v7.0.0...v7.1.0
Configuration
📅 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 has been generated by Mend Renovate. View repository job log here.