chore(deps): update npm packages #1074
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/npm
branch
9 times, most recently
from
c8419be
to
0101839
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm
branch
11 times, most recently
from
4d318f9
to
8e573e8
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
8 times, most recently
from
6471947
to
78f7b26
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
13 times, most recently
from
7ad016d
to
63a0eb4
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
10 times, most recently
from
20c0e77
to
0f95d6f
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
4 times, most recently
from
1872f0c
to
8c9df69
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
from
8c9df69
to
455f185
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^29.5.12->^29.5.14^20.12.7->^20.17.58.8.0->8.12.28.8.0->8.12.2^18.3.1->^18.4.0^9.4.0->^9.8.0^9.9.1->^9.13.0^14.1.0->^14.2.4^3.4.4->^3.5.09.7.0->9.12.3^29.1.2->^29.2.5^2.6.2->^2.8.1~5.4.5->~5.6.3^8.8.1->^8.12.2Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.12.2Compare Source
🩹 Fixes
considerDefaultExhaustiveForUnions(#10223)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.12.1Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.12.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.11.0Compare Source
🚀 Features
🩹 Fixes
overridekeyword (#10135)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.10.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.9.0Compare Source
🩹 Fixes
eslint-plugin: [no-unnecessary-type-parameters] cannot assume variables are either type or value
scope-manager: [no-use-before-define] do not treat nested namespace aliases as variable references
eslint-plugin: [return-await] sync the behavior with await-thenable
eslint-plugin: [prefer-literal-enum-member] report a different error message when
allowBitwiseExpressionsis enabledeslint-plugin: [no-loop-func] sync from upstream base rule
eslint-plugin: [no-unused-vars] never report the naming of an enum member
eslint-plugin: correct use-at-your-own-risk type definitions
eslint-plugin: handle unions in await...for
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.8.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.12.2Compare 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.
v8.12.1Compare 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.
v8.12.0Compare 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.
v8.11.0Compare 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.
v8.10.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.9.0Compare 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.
v8.8.1Compare 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.
angular-eslint/angular-eslint (angular-eslint)
v18.4.0Compare Source
This was a version bump only for angular-eslint to align it with other projects, there were no code changes.
antfu/bumpp (bumpp)
v9.8.0Compare Source
🚀 Features
View changes on GitHub
v9.7.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.7.0Compare Source
🚀 Features
View changes on GitHub
v9.6.1Compare Source
🚀 Features
View changes on GitHub
v9.6.0Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v9.5.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.5.1Compare Source
🚀 Features
View changes on GitHub
v9.5.0Compare Source
v9.4.2Compare Source
v9.4.1Compare Source
eslint/eslint (eslint)
v9.13.0Compare Source
thymikee/jest-preset-angular (jest-preset-angular)
v14.2.4Compare Source
Bug Fixes
v14.2.3Compare Source
Bug Fixes
v14.2.2Compare Source
Bug Fixes
v14.2.1Compare Source
Bug Fixes
isolatedModules: true(31e78b1)v14.2.0Compare Source
Features
Code Refactoring
ng-snapshot(3ce21cd)v14.1.1Compare Source
Features
moment/luxon (luxon)
v3.5.0Compare Source
pnpm/pnpm (pnpm)
v9.12.3Compare Source
Patch Changes
node_modules, when typing "n" in the prompt that asks whether to removenode_modulesbefore installation #8655.manage-package-manager-versions=trueis set and the.toolsdirectory is corrupt.crypto.hash, when available, for improved performance #8629.package.jsonat the root of the workspace #8667.manage-package-manager-versionsis set totrue, errors spawning a self-managed version ofpnpmwill now be shown (instead of being silent).v9.12.2Compare Source
Patch Changes
v9.12.1Compare Source
Patch Changes
pnpm update --latestshould not update the automatically installed peer dependencies #6657.pnpm publishshould be able to publish from a local tarball #7950.EBUSYerrors caused by creating symlinks in paralleldlxprocesses #8604.v9.12.0Compare Source
Minor Changes
Fix peer dependency resolution dead lock #8570. This change might change some of the keys in the
snapshotsfield insidepnpm-lock.yamlbut it should happen very rarely.pnpm outdatedcommand supports now a--sort-by=nameoption for sorting outdated dependencies by package name #8523.Added the ability for
overridesto remove dependencies by specifying"-"as the field value #8572. For example, to removelodashfrom the dependencies, use this configuration inpackage.json:{ "pnpm": { "overrides": { "lodash": "-" } } }Patch Changes
pnpm list --json pkgshowed"private": falsefor a private package #8519.libcthat differ frompnpm.supportedArchitectures.libcare not downloaded #7362.ENOENTerrors caused by runningstore prunein parallel #8586.pnpm bugs#8596.v9.11.0Compare Source
Minor Changes
pnpm cachecommands for inspecting the metadata cache #8512.Patch Changes
pnpm deploywithnode-linker=hoistedproduces an emptynode_modulesdirectory #6682.pnpm deployshould work in workspace withshared-workspace-lockfile=false#8475.v9.10.0Compare Source
Minor Changes
Support for a new CLI flag,
--exclude-peers, added to thelistandwhycommands. When--exclude-peersis used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.Added a new setting to
package.jsonatpnpm.auditConfig.ignoreGhsasfor ignoring vulnerabilities by their GHSA code #6838.For instance:
{ "pnpm": { "auditConfig": { "ignoreGhsas": [ "GHSA-42xw-2xvc-qx8m", "GHSA-4w2v-q235-vp99", "GHSA-cph5-m8f7-6c5x", "GHSA-vh95-rmgr-6w4m" ] } } }Patch Changes
v9.9.0Compare Source
Minor Changes
Minor breaking change. This change might result in resolving your peer dependencies slightly differently but we don't expect it to introduce issues.
We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.
When a peer dependency is a prod dependency somewhere in the dependency graph (with the same version), pnpm will resolve the peers of that peer dependency in the same way across the subgraph.
For example, we have
react-domin the peer deps of theformandbuttonpackages.cardhasreact-domandreactas regular dependencies andcardis a dependency ofform.These are the direct dependencies of our example project:
These are the dependencies of card:
When resolving peers, pnpm will not re-resolve
react-domforcard, even thoughcardshadowsreact@16from the root withreact@17. So, all 3 packages (form,card, andbutton) will usereact-dom@16, which in turn usesreact@16.formwill usereact@16, whilecardandbuttonwill usereact@17.Before this optimization
react-dom@16was duplicated for thecard, so thatcardandbuttonwould use areact-dom@16instance that usesreact@17.Before the change:
After the change
Patch Changes
pnpm deployshould write thenode_modules/.modules.yamlto thenode_modulesdirectory within the deploy directory #7731.node_modulesif it already points to the right location pnpm/symlink-dir#54.v9.8.0Compare Source
Minor Changes
Added a new command for upgrading pnpm itself when it isn't managed by Corepack:
pnpm self-update. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #8424.When executed in a project that has a
packageManagerfield in itspackage.jsonfile, pnpm will update its version in thepackageManagerfield.Patch Changes
CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and
use-node-versionis set.pnpm setupshould never switch to another version of pnpm.This fixes installation with the standalone script from a directory that has a
package.jsonwith thepackageManagerfield. pnpm was installing the version of pnpm specified in thepackageManagerfield due to this issue.Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #8431.
Remember the state of edit dir, allow running
pnpm patch-committhe second time without having to re-runpnpm patch.v9.7.1Compare Source
Patch Changes
public-hoist-patternandhoist-patternvia env variables #8339.pnpm setupno longer creates Batch/Powershell scripts on Linux and macOS #8418.pnpm execnow supports executionEnv #8356.pnpmfield, add warnings for non-rootpnpmsubfields that aren'texecutionEnv#8143.patch-commitin which relative path is rejected #8405.@pnpm/exeto v20.kulshekhar/ts-jest (ts-jest)
v29.2.5Compare Source
v29.2.4Compare Source
v29.2.3Compare Source
v29.2.2Compare Source
v29.2.1Compare Source
v29.2.0Compare Source
Bug Fixes
Features
presetstotransformconfig (22fb027)Code refactoring
TsJestTransformerOptionstype everywhere possibly (7d001be)react-appto use Vite (827c8ad)v29.1.5Compare Source
Bug Fixes
v29.1.4Compare Source
Bug Fixes
Features
type: "module"(#4210) (81a5f64), closes #4210 #4012v29.1.3Compare Source
Bug Fixes
@jest/transformas an optional peer dependency (0ba7f86)Performance Improvements
Microsoft/tslib (tslib)
v2.8.1Compare Source
v2.8.0Compare Source
What's Changed
Full Changelog: microsoft/tslib@v2.7.0...v2.8.0
v2.7.0Compare Source
v2.6.3Compare Source
What's Changed
Full Changelog: microsoft/tslib@v2.6.2...v2.6.3
microsoft/TypeScript (typescript)
v5.6.3Compare Source
v5.6.2Compare Source
v5.5.4: TypeScript 5.5.4Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
v5.5.3: TypeScript 5.5.3Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
v5.5.2: TypeScript 5.5Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
typescript-eslint/typescript-eslint (typescript-eslint)
v8.12.2Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.12.1Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.12.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.11.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.10.0Compare Source
🩹 Fixes
namefield to extended configs inconfighelper (#10094)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.9.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
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 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 was generated by Mend Renovate. View the repository job log.