fix(deps): update all non-major dependencies #14635
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:
^7.23.0
->^7.23.2
^7.22.20
->^7.23.2
^7.23.1
->^7.23.2
^2.5.0
->^2.6.0
^25.0.5
->^25.0.7
^2.0.6
->^2.0.7
^18.18.4
->^18.18.5
^2.4.5
->^2.4.6
^18.2.25
->^18.2.28
^18.2.11
->^18.2.13
^8.5.6
->^8.5.7
^6.7.4
->^6.7.5
^6.7.4
->^6.7.5
^16.1.0
->^16.2.0
^0.30.4
->^0.30.5
^0.30.4
->^0.30.5
^3.20231002.1
->^3.20231010.0
^1.7.7
->^1.7.9
^1.38.1
->^1.39.0
8.8.0
->8.9.2
^3.1.0
->^3.2.0
^1.69.0
->^1.69.3
^1.7.12
->^1.8.1
v39.2.1
->v39.2.2
^5.0.0-beta.4
->^5.0.0-beta.7
^2.7.0
->^2.7.1
1.0.0-rc.20
->1.0.0-rc.22
^1.8.18
->^1.8.19
Release Notes
babel/babel (@babel/core)
v7.23.2
Compare Source
🐛 Bug Fix
babel-traverse
babel-preset-typescript
.tsx
extension when usingrewriteImportExtensions
(@jimmydief)babel-helpers
babel-helpers
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
preactjs/preset-vite (@preact/preset-vite)
v2.6.0
Compare Source
Features
Fixes
rollup/plugins (@rollup/plugin-commonjs)
v25.0.7
Compare Source
2023-10-15
Bugfixes
v25.0.6
Compare Source
2023-10-15
Bugfixes
rollup/plugins (@rollup/plugin-dynamic-import-vars)
v2.0.7
Compare Source
2023-10-15
Bugfixes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.7.5
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.7.5
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
eslint-community/eslint-plugin-n (eslint-plugin-n)
v16.2.0
Compare Source
Features
6d02512
)Bugfixes
package.json#files
before checking ignores and whitelist (#123) (fixes #122) (2d43f48
)Docs & Chores
codecov
(#125) (5507f43
)574df88
)npm-run-all
fork (#124) (98ea90e
)actions/setup-node
setup for linting (7f54d0c
)4f3891c
)7d855e6
)150b34f
)b7d0536
)rich-harris/magic-string (magic-string)
v0.30.5
Compare Source
Bug Fixes
sourcesContent
type (#263) (0e2068d)cloudflare/miniflare (miniflare)
v3.20231010.0
Compare Source
phoenixframework/phoenix (phoenix)
v1.7.9
Compare Source
Bug fixes
--no-html
pas passedv1.7.8
Compare Source
Bug fixes
mix phx.gen.release --docker
failing with:http_util
error on Elixir v1.15th
for actions if actions are emptyEnhancements
plug_crypto
~p
--repo
and--migration-dir
flags<.input type="checkbox">
withoutvalue
attr in core components--adapter
flag for generating application with bandit--method
optionmicrosoft/playwright (playwright-chromium)
v1.39.0
Compare Source
Add custom matchers to your expect
You can extend Playwright assertions by providing custom matchers. These matchers will be available on the expect object.
See the documentation for a full example.
Merge test fixtures
You can now merge test fixtures from multiple files or modules:
Merge custom expect matchers
You can now merge custom expect matchers from multiple files or modules:
Hide implementation details: box test steps
You can mark a
test.step()
as "boxed" so that errors inside it point to the step call site.Error: Timed out 5000ms waiting for expect(locator).toBeVisible() ... error details omitted ... 14 | await page.goto('https://github.com/login'); > 15 | await login(page); | ^ 16 | });
See
test.step()
documentation for a full example.New APIs
expect(locator).toHaveAttribute(name)
Browser Versions
This version was also tested against the following stable channels:
pnpm/pnpm (pnpm)
v8.9.2
Compare Source
Patch Changes
preinstall
lifecycle script is present #7206.Our Gold Sponsors
Our Silver Sponsors
v8.9.1
Compare Source
Patch Changes
pnpm update --interactive
7109shared-workspace-lockfile
is set tofalse
, read the pnpm settings frompackage.json
files that are nested. This was broken in pnpm v8.9.0 #7184.node_modules
on Windows Dev Drives #7186. This is a fix to a regression that was shipped with v8.9.0.pnpm dlx
should ignore any settings that are in apackage.json
file found in the current working directory #7198.Our Gold Sponsors
Our Silver Sponsors
v8.9.0
Compare Source
Minor Changes
🚀Performance improvement: Use reflinks instead of hard links by default on macOS and Windows Dev Drives #5001.
The list of packages that are allowed to run installation scripts now may be provided in a separate configuration file. The path to the file should be specified via the
pnpm.onlyBuiltDependenciesFile
field inpackage.json
. For instance:In the example above, the list is loaded from a dependency. The JSON file with the list should contain an array of package names. For instance:
With the above list, only
esbuild
and@reflink/reflink
will be allowed to run scripts during installation.Related issue: #7137.
Add
disallow-workspace-cycles
option to error instead of warn about cyclic dependenciesAllow
env rm
to remove multiple node versions at once, and introduceenv add
for installing node versions without setting as default #7155.Patch Changes
pnpm why
when the dependencies tree is too big, the command will now prune the tree to just 10 end leafs and now supports--depth
argument #7122.neverBuiltDependencies
andonlyBuiltDependencies
from the rootpackage.json
of the workspace, whenshared-workspace-lockfile
is set tofalse
#7141.pnpm.overrides
replacingresolutions
, the two are now merged. This is intended to make it easier to migrate from Yarn by allowing one to keep usingresolutions
for Yarn, but adding additional changes just for pnpm usingpnpm.overrides
.Our Gold Sponsors
Our Silver Sponsors
mjeanroy/rollup-plugin-license (rollup-plugin-license)
v3.2.0
Compare Source
sass/dart-sass (sass)
v1.69.3
Compare Source
Embedded Sass
package.json
.v1.69.2
Compare Source
JS API
variable named
process
.v1.69.1
Compare Source
solidjs/solid (solid-js)
v1.8.0
Compare Source
I admit this is not the most exciting release from a feature standpoint. We are in that holding pattern between the end of 1.x and the start of 2.0. We recently made our new reactive experiments public and continue to build those out in public with @solidjs/signals.
This version is more about addressing some of the fundamentals that will help us in other projects like SolidStart while we do the transition. A big part of this is applying what we have learned when doing performance benchmarks for the work that has been funded by Google Chrome Aurora.
Async and Resources need work and are too all in. It is great to have a solution but now that we have a better understanding we need to start breaking things apart into their fundamental pieces.
De-duping Streaming Serialization
This is the marquee feature of this release and is largely the work of @lxsmnsyc. Solid has been able to serialize promises and do streaming for a couple of years now, but it was very special-cased. Now it is a generic mechanism.
This matters because it means that we have decoupled the promise serialization from Resources, and in so decoupled the whole when the stream is done from them. This opens up things like nested promises.
More so we have a mechanism now that deeply de-dupes data serialized across flushes. This is important for features like Islands where you might pass the same props to multiple Islands across different Suspense boundaries and don't want to send the data more than once. And even examples where that data can be accessed at varying depths (recursive comments in say a Hackernews site).
Hydration Improvements
Fragments for Hydration have been a bit of a pain and we keep seeming to have different issues reported around element duplication. Most commonly this has been around where there are
lazy
component siblings or where the fragment is top-level. After looking into and fixing an issue for Astro I decided to look at some of the oldest bugs in Solid and found it was a similar bug.In many cases, the DOM can change throughout Hydration while doing things like streaming but we need to pause and resume hydration because code isn't available yet. While we don't create elements during hydration, getting an accurate snapshot of the DOM for the current state for future list reconciliation is a process we've had a few tries at but in 1.8 we update this in a way that makes sure it doesn't get out of date.
Also in 1.8, we have added some performance improvements to hydration in the form of not redundantly setting attributes or props as the page hydrates similar to how we don't update text. This is all migration towards a future where we don't need to do as much hydration, but it is important to note that values will be kept as they were on the server rather than how they may compute at runtime during hydration.
Smaller Templates
In 1.7 we removed unnecessary closing tags from template st
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 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.