chore(npm) Update NPM #119
Open
Conversation
This file contains hidden or 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
from
5d3593d to
259bf07
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
5 times, most recently
from
1ed4814 to
5cb77df
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
3 times, most recently
from
d41fe41 to
66ffecd
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
3 times, most recently
from
abbc456 to
dfa128b
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
4 times, most recently
from
c53d27e to
6868863
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
3 times, most recently
from
4c83ecb to
6c72be7
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
5 times, most recently
from
a31bbd6 to
5061daa
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
from
5061daa to
212905c
Compare
renovate
bot
force-pushed
the
renovate/npm
branch
from
212905c to
08a3965
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.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
8.20.1->8.22.48.20.1->8.22.48.20.1->8.22.48.20.1->8.22.47.0.1->7.3.09.32.0->9.37.030.0.5->30.2.030.0.5->30.2.016.1.2->16.2.38.20.1->8.22.4Release Notes
salesforce/lwc (@lwc/compiler)
v8.22.4Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.22.3...v8.22.4
v8.22.3Compare Source
What's Changed
TestUtilsfrom hydration tests @W-19098266 by @wjhsf in #5489Full Changelog: salesforce/lwc@v8.22.1...v8.22.3
v8.22.1Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.21.6...v8.22.1
v8.21.6Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.21.5...v8.21.6
v8.21.4Compare Source
Full Changelog: salesforce/lwc@v8.21.3...v8.21.4
v8.21.3Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.21.2...v8.21.3
v8.21.2Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.21.1...v8.21.2
v8.21.1Compare Source
What's Changed
masterby @jmsjtu in #5447Full Changelog: salesforce/lwc@v8.20.3...v8.21.1
v8.20.5Compare Source
What's Changed
winter26dist tag to nucleus by @jmsjtu in #5458Full Changelog: salesforce/lwc@v8.20.4...v8.20.5
v8.20.4Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.20.3...v8.20.4
v8.20.3Compare Source
What's Changed
v8.20.2Compare Source
What's Changed
syntheticprop to component template by @wjhsf in #5426New Contributors
Full Changelog: salesforce/lwc@v8.20.1...v8.20.2
salesforce/sfdx-lwc-jest (@salesforce/sfdx-lwc-jest)
v7.3.0Compare Source
What's Changed
New Contributors
Full Changelog: salesforce/sfdx-lwc-jest@v7.2.0...v7.3.0
v7.1.1Compare Source
What's Changed
winter26by @jmsjtu in #445Full Changelog: salesforce/sfdx-lwc-jest@v7.1.0...v7.1.1
v7.1.0Compare Source
What's Changed
No meaningful changes. The previous release should have been a minor release, rather than patch.
Full Changelog: salesforce/sfdx-lwc-jest@v7.0.2...v7.1.0
v7.0.2Compare Source
What's Changed
Full Changelog: salesforce/sfdx-lwc-jest@v7.0.1...v7.0.2
eslint/eslint (eslint)
v9.37.0Compare Source
v9.36.0Compare Source
v9.35.0Compare Source
v9.34.0Compare Source
v9.33.0Compare Source
jestjs/jest (jest)
v30.2.0Compare Source
Chore & Maintenance
[*]Update example repo for testing React Native projects (#15832)[*]Updatejest-watch-typeaheadto v3 (#15830)v30.1.3Compare Source
Fixes
unstable_mockModulewithnode:prefixed core modules.v30.1.2Compare Source
v30.1.1Compare Source
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)v30.1.0Compare Source
lint-staged/lint-staged (lint-staged)
v16.2.3Compare Source
Patch Changes
27cd541Thanks @iiroj! - When using--fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.v16.2.2Compare Source
Patch Changes
#1667
699f95dThanks @iiroj! - The backup stash will not be dropped when using--fail-on-changesand there are errors. When reverting to original state is disabled (via--no-revertor--fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:
v16.2.1Compare Source
Patch Changes
#1664
8277b3bThanks @iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions isreadonly string[]and can't be mutated. Thanks @outslept!export default { --- "*": (files: string[]) => void console.log('staged files', files) +++ "*": (files: readonly string[]) => void console.log('staged files', files) }#1654
70b9af3Thanks @iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.#1659
4996817Thanks @iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there arepackage.jsonfiles in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.#1654
7021f0aThanks @iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues withchalkanddebug, which were also removed in the same version.Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.
v16.2.0Compare Source
Minor Changes
#1615
99eb742Thanks @iiroj! - Added a new option--fail-on-changesto make lint-staged exit with code 1 when tasks modify any files, making theprecommithook fail. This is similar to thegit diff --exit-codeoption. Using this flag also implies the--no-revertflag which means any changes made my tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.#1611
cd05fd3Thanks @rlorenzo! - Added a new option--continue-on-errorso that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.#1637
82fcc07Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.#1647
a5ecc06Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, theDEBUGenvironment variable is no longer supported — use the--debugto enable debugging#1636
8db2717Thanks @iiroj! - Added a new option--hide-unstagedso that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags--hide-unstaged --no-hide-partially-stagedisn't meaningful and behaves the same as just--hide-unstaged.Thanks to @ItsNickBarry for the idea and initial implementation in #1552.
#1648
7900b3bThanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.Patch Changes
#1633
7f9e485Thanks @dependabot! - Bumps listr2 from 9.0.3 to 9.0.4.#1626
99d5a9bThanks @iiroj! - Due to recent phishing attacks, for example [email protected] was released with malware. To avoid lint-staged's users being at risk the direct dependencies are pinned to exact versions, instead of allowing future patch versions with the caret (^) range.#1588
035bbf2Thanks @outslept! - Increase performance by listing staged files and searching for configuration concurrently.#1645
deba3adThanks @iiroj! - Remove chalk as a dependency due to recent malware issue; read more at chalk/chalk#656.If you are having trouble with ANSI color codes when using lint-staged, you can try setting either
FORCE_COLOR=trueorNO_COLOR=trueenv variables.v16.1.6Compare Source
Patch Changes
e93578eThanks @iiroj! - Try to improve terminating of subprocess of tasks by usingSIGKILL, and only callingpidtreewhen the the main task process has a known pid.v16.1.5Compare Source
Patch Changes
4e3ce22Thanks @srsatt! - Detect the git repo's top-level directory correctly when in a worktree.v16.1.4Compare Source
Patch Changes
90b37b0Thanks @iiroj! - Add anothertypesfield topackage.jsonto make even more sure NPM detects that lint-staged includes built-in TypeScript type definitions.v16.1.3Compare Source
Patch Changes
7ea700bThanks @dword-design! - Add thetypesfield topackage.jsonto make sure NPM detects lint-staged includes built-in TypeScript type definitions.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.