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:
^1.8.0
->^1.8.3
^1.5.11
->^1.5.12
^3.2.0
->^3.2.3
^3.2.0
->^3.2.3
^3.2.0
->^3.2.3
^5.50.0
->^5.54.0
^5.50.0
->^5.54.0
^8.34.0
->^8.35.0
^3.2.0
->^3.2.3
7.26.3
->7.28.0
^2.8.3
->^2.8.4
^0.28.4
->^0.29.2
Release Notes
ForestAdmin/agent-nodejs (@forestadmin/agent)
v1.8.3
Compare Source
Dependencies
v1.8.2
Compare Source
Bug Fixes
v1.8.1
Compare Source
Bug Fixes
Dependencies
ForestAdmin/agent-nodejs (@forestadmin/datasource-customizer)
v1.5.12
Compare Source
nuxt/nuxt
v3.2.3
Compare Source
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
distDir
is unlinked (#19131)<NuxtLink>
(#19144)rel
attribute on internal link (#19309)noExternal
option (#19256)📖 Documentation
🏡 Chore
🤖 CI
❤️ Contributors
v3.2.2
Compare Source
👀 Highlights
As a patch release, there are mostly bug fixes and performance improvements in the changelog. (Nevertheless, it's always worth reading through!) But one point of note is an experimental reload strategy when chunk errors are encountered. We're hoping to finalise the API and land it in v3.3 (our next feature release) with https://github.com/nuxt/nuxt/pull/19086, but you can test out an experimental version with the following config:
With this strategy, your app will hard reload on route changes if there's a chunk error. More info at https://github.com/nuxt/nuxt/pull/19038.
👉 Changelog
compare changes
🚀 Enhancements
app:chunkError
hook and reload strategy (#19038)🔥 Performance
#components
(#19008)🩹 Fixes
nuxt/schema
subpath for augmentation (#18922)statusCode
is a number (#19001)nuxt/app
by default (#19009)nuxt/app
from optimised deps (9e789c76c)isCustomElement
config for jsx transform (#19053)devServer
options from nuxt config (#19055)//
in path when constructing payload url (#19085)💅 Refactors
📖 Documentation
nuxi devtools
command (#18888)static
property (80f73d39c)sendRedirect
usage (#19070)📦 Build
nuxt/schema
to externals (e3e768873)nuxt
to nuxt externals (b1b908b1e)🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
v3.2.1
Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.54.0
Compare Source
Features
v5.53.0
Compare Source
Features
v5.52.0
Compare Source
Bug Fixes
Features
v5.51.0
Compare Source
Bug Fixes
Features
verbatimModuleSyntax
(#6394) (b14d3be)typescript-eslint/typescript-eslint (@typescript-eslint/parser)
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
v5.51.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
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)pnpm/pnpm
v7.28.0
Compare Source
Minor Changes
--report-summary
forpnpm exec
andpnpm run
#6008.pnpm why --json
or--long
#6103.pnpm.peerDependencyRules.allowedVersions
package.json
option to support theparent>child
selector syntax. This syntax allows for extending specificpeerDependencies
#6108.Patch Changes
peerDependenciesMeta
and notpeerDependencies
,dependencies
, oroptionalDependencies
, the dependency's peers were not considered deterministically before.patch-commit
should auto apply patches in workspaces #6048pnpm config set
should write to the global config file by default #5877.Our Gold Sponsors
Our Silver Sponsors
v7.27.1
Compare Source
Patch Changes
store path
description to thepnpm
cli help.pnpm store prune
, when a tarball integrity error happens.strict-ssl
,ca
,key
, andcert
settings should work with HTTPS proxy servers #4689.Our Gold Sponsors
Our Silver Sponsors
v7.27.0
Compare Source
Minor Changes
resolution-mode
added:lowest-direct
. With this resolution mode direct dependencies will be resolved to their lowest versions. So if there isfoo@^1.1.0
in the dependencies, then1.1.0
will be installed, even if the latest version offoo
is1.2.0
.pnpm run /build:.*/
and execute the matched scripts with the RegExp #5871.Patch Changes
Fix version number replacing for namespaced workspace packages.
workspace:@​foo/bar@*
should be replaced withnpm:@​foo/bar@<version>
on publish #6052.When resolving dependencies, prefer versions that are already used in the root of the project. This is important to minimize the number of packages that will be nested during hoisting #6054.
Deduplicate direct dependencies.
Let's say there are two projects in the workspace that dependend on
foo
. One project hasfoo@1.0.0
in the dependencies while another one hasfoo@^1.0.0
in the dependencies. In this case,foo@1.0.0
should be installed to both projects as satisfies the version specs of both projects.Use Map rather than Object in
createPackageExtender
to prevent read the prototype property to native functionOur Gold Sponsors
Our Silver Sponsors
prettier/prettier
v2.8.4
Compare Source
diff
Fix leading comments in mapped types with
readonly
(#13427 by @thorn0, @sosukesuzuki)Group params in opening block statements (#14067 by @jamescdavis)
This is a follow-up to #13930 to establish wrapping consistency between opening block statements and else blocks by
grouping params in opening blocks. This causes params to break to a new line together and not be split across lines
unless the length of params exceeds the print width. This also updates the else block wrapping to behave exactly the
same as opening blocks.
Ignore files in
.sl/
(#14206 by @bolinfest)In Sapling SCM,
.sl/
is the folder where it stores its state, analogous to.git/
in Git. It should be ignored in Prettier like the other SCM folders.Recognize
@satisfies
in Closure-style type casts (#14262 by @fisker)Fix parens in inferred function return types with
extends
(#14279 by @fisker)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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.