chore(deps): update all non-major dependencies #151
Merged
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:
^18.13.0
->^18.14.3
^5.51.0
->^5.54.0
^0.28.4
->^0.29.2
^0.17.6
->^0.17.10
^8.33.0
->^8.35.0
^4.6.0
->^4.6.1
^15.6.0
->^15.7.0
^0.28.4
->^0.29.2
Release Notes
typescript-eslint/typescript-eslint
v5.54.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.53.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.52.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
vitest-dev/vitest
v0.29.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.0
Compare Source
This release makes some significant changes to how tests are running. If you were using
--no-threads
before, you might consider enabling--single-thread
instead (because your tests are now running inchild_process
instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (likeprocess.chdir()
, you can now use this option.One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with
--no-isolate
,--no-threads
or--single-thread
- you might need to update your setup files if you were relying on a global variable before.If you had performance issues on large code bases before, try the new
deps.experimentalOptimizer
option instead of disabling threads. Feedback is welcome!One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.
🚨 Breaking Changes
NODE_V8_COVERAGE
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2786 (095c6)node
andjsdom
(and other environments) now don't share the same global scope, if you run them with--no-isolate
or--no-threads
flag. Vitest doesn't provide a way to restore the previous behavior as it is considered a bug.chid_process
might run longer due to the communication overhead. If you want to restore the previous behavior, use--single-thread
.🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.28.5
Compare Source
🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub
evanw/esbuild
v0.17.10
Compare Source
Update esbuild's handling of CSS nesting to match the latest specification changes (#1945)
The syntax for the upcoming CSS nesting feature has recently changed. The
@nest
prefix that was previously required in some cases is now gone, and nested rules no longer have to start with&
(as long as they don't start with an identifier or function token).This release updates esbuild's pass-through handling of CSS nesting syntax to match the latest specification changes. So you can now use esbuild to bundle CSS containing nested rules and try them out in a browser that supports CSS nesting (which includes nightly builds of both Chrome and Safari).
However, I'm not implementing lowering of nested CSS to non-nested CSS for older browsers yet. While the syntax has been decided, the semantics are still in flux. In particular, there is still some debate about changing the fundamental way that CSS nesting works. For example, you might think that the following CSS is equivalent to a
.outer .inner button { ... }
rule:But instead it's actually equivalent to a
.outer :is(.inner button) { ... }
rule which unintuitively also matches the following DOM structure:The
:is()
behavior is preferred by browser implementers because it's more memory-efficient, but the straightforward translation into a.outer .inner button { ... }
rule is preferred by developers used to the existing CSS preprocessing ecosystem (e.g. SASS). It seems premature to commit esbuild to specific semantics for this syntax at this time given the ongoing debate.Fix cross-file CSS rule deduplication involving
url()
tokens (#2936)Previously cross-file CSS rule deduplication didn't handle
url()
tokens correctly. These tokens contain references to import paths which may be internal (i.e. in the bundle) or external (i.e. not in the bundle). When comparing twourl()
tokens for equality, the underlying import paths should be compared instead of their references. This release of esbuild fixesurl()
token comparisons. One side effect is that@font-face
rules should now be deduplicated correctly across files:v0.17.9
Compare Source
Parse rest bindings in TypeScript types (#2937)
Previously esbuild was unable to parse the following valid TypeScript code:
This release includes support for parsing code like this.
Fix TypeScript code translation for certain computed
declare
class fields (#2914)In TypeScript, the key of a computed
declare
class field should only be preserved if there are no decorators for that field. Previously esbuild always preserved the key, but esbuild will now remove the key to match the output of the TypeScript compiler:Fix a crash with path resolution error generation (#2913)
In certain situations, a module containing an invalid import path could previously cause esbuild to crash when it attempts to generate a more helpful error message. This crash has been fixed.
v0.17.8
Compare Source
Fix a minification bug with non-ASCII identifiers (#2910)
This release fixes a bug with esbuild where non-ASCII identifiers followed by a keyword were incorrectly not separated by a space. This bug affected both the
in
andinstanceof
keywords. Here's an example of the fix:Fix a regression with esbuild's WebAssembly API in version 0.17.6 (#2911)
Version 0.17.6 of esbuild updated the Go toolchain to version 1.20.0. This had the unfortunate side effect of increasing the amount of stack space that esbuild uses (presumably due to some changes to Go's WebAssembly implementation) which could cause esbuild's WebAssembly-based API to crash with a stack overflow in cases where it previously didn't crash. One such case is the package
grapheme-splitter
which contains code that looks like this:This edge case involves a chain of binary operators that results in an AST over 400 nodes deep. Normally this wouldn't be a problem because Go has growable call stacks, so the call stack would just grow to be as large as needed. However, WebAssembly byte code deliberately doesn't expose the ability to manipulate the stack pointer, so Go's WebAssembly translation is forced to use the fixed-size WebAssembly call stack. So esbuild's WebAssembly implementation is vulnerable to stack overflow in cases like these.
It's not unreasonable for this to cause a stack overflow, and for esbuild's answer to this problem to be "don't write code like this." That's how many other AST-manipulation tools handle this problem. However, it's possible to implement AST traversal using iteration instead of recursion to work around limited call stack space. This version of esbuild implements this code transformation for esbuild's JavaScript parser and printer, so esbuild's WebAssembly implementation is now able to process the
grapheme-splitter
package (at least when compiled with Go 1.20.0 and run with node's WebAssembly implementation).eslint/eslint
v8.35.0
Compare Source
Features
8e34a04
feat: addafterHashbangComment
option tolines-around-comment
rule (#16920) (SUZUKI Sosuke)c8c0c71
feat: Move all and recommended configs into package. (#16844) (Nicholas C. Zakas)71f6f0d
feat: report more cases with??
in no-constant-binary-expression (#16826) (Daiki Nishikawa)Bug Fixes
9698bc5
fix: pin esquery v1.4.0 (fixes #16896) (#16897) (唯然)Documentation
f9f195e
docs: Plugin docs cleanup & expansion (#16862) (Ben Perlmutter)df809fd
docs: Custom Formatters page cleanup/expansion (#16886) (Ben Perlmutter)0700d1b
docs: Add PostCSS/Autoprefixer/CSSNano (#16502) (Nick Schonning)7b9e9bf
docs: support unicode anchors (#16782) (Percy Ma)5fbc0bf
docs: Update README (GitHub Actions Bot)67865a0
docs: Remove mention of mailing list (#16869) (Amaresh S M)43af24a
docs: Add explanation of when to use 'warn' severity (#16882) (Nicholas C. Zakas)ed2999b
docs: Shareable configs page edits and expansion (#16824) (Ben Perlmutter)2780635
docs: fix typos (#16884) (Lioness100)5bdaae2
docs: Ways to Extend ESLint page (#16861) (Ben Perlmutter)Chores
cdcbe12
chore: upgrade @eslint/js@8.35.0 (#16935) (Brandon Mills)c954c34
chore: package.json update for @eslint/js release (ESLint Jenkins)5a517da
chore: package.json update for @eslint/js release (ESLint Jenkins)9f10926
chore: upgrade @eslint/eslintrc@2.0.0 (#16928) (Milos Djermanovic)da728fa
ci: use LTS node version in workflows (#16907) (Nitin Kumar)c57b4f3
perf: upgrade to esquery@1.4.2 (#16901) (Milos Djermanovic)9122f07
chore: Update stale bot settings (#16870) (Nicholas C. Zakas)github/eslint-plugin-github
v4.6.1
Compare Source
What's Changed
no-useless-passive
andrequire-passive-events
by @boris-petrov in https://github.com/github/eslint-plugin-github/pull/354role-supports-aria-props
rule (noaria-label
-misuse) by @smockle in https://github.com/github/eslint-plugin-github/pull/362New Contributors
Full Changelog: github/eslint-plugin-github@v4.6.0...v4.6.1
release-it/release-it
v15.7.0
Compare Source
f4702c4
)7076fd3
)81a7d69
)0a23c55
)v15.6.1
Compare Source
554c600
)npm list collaborators
diff in npm v8 vs v9 in tests (1935621
)1e6dca8
)peerDependencies
property (#980) (7784c97
)2a8271f
)b525c25
)Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" in timezone Pacific/Auckland, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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.