Skip to content

chore(deps): update devdependencies#125

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/devdependencies
Open

chore(deps): update devdependencies#125
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/devdependencies

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 17, 2022

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm-check-updates 16.5.619.6.3 age adoption passing confidence
prettier-config-atomic ^3.0.6^4.0.0 age adoption passing confidence
typescript (source) ^4.2.3^5.0.0 age adoption passing confidence

Release Notes

raineorshine/npm-check-updates (npm-check-updates)

v19.6.3

Compare Source

Full Changelog: raineorshine/npm-check-updates@v19.6.2...v19.6.3

v19.6.2

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v19.6.1...v19.6.2

v19.6.1

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v19.6.0...v19.6.1

v19.6.0

Compare Source

What's Changed

  • Display link to compare the changes between package versions (--format diff) by @​diegocr in #​1602

New Contributors

Full Changelog: raineorshine/npm-check-updates@v19.5.0...v19.6.0

v19.5.0

Compare Source

What's Changed

  • feat(homepage): Add --format homepage option to print homepage.

e.g.

$ ncu --format homepage
...
 mocha                      ^11.7.2  →   ^11.7.5    https://mochajs.org/
 npm-registry-fetch         ^19.0.0  →   ^19.1.1
 prettier                   ^3.6.2  →    ^3.8.1     https://prettier.io
...

Full Changelog: raineorshine/npm-check-updates@v19.4.1...v19.5.0

v19.4.1

Compare Source

What's Changed

  • Fixed a small cooldown regression with number types in the ncurc

Full Changelog: raineorshine/npm-check-updates@v19.4.0...v19.4.1

v19.4.0

Compare Source

What's Changed

New Contributors

Full Changelog: raineorshine/npm-check-updates@v19.3.2...v19.4.0

v19.3.2

Compare Source

What's Changed

  • docs: close code tag instead of reopening another one by @​sod in #​1588
  • fix(tests): resolve EBUSY errors on Windows by retrying directory removal by @​Zamiell in #​1590

New Contributors

Full Changelog: raineorshine/npm-check-updates@v19.3.1...v19.3.2

v19.3.1

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v19.3.0...v19.3.1

v19.3.0

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v19.2.1...v19.3.0

v19.2.1

Compare Source

Full Changelog: raineorshine/npm-check-updates@v19.2.0...v19.2.1

v19.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: raineorshine/npm-check-updates@v19.1.2...v19.2.0

v19.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: raineorshine/npm-check-updates@v19.1.1...v19.1.2

v19.1.1

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v19.1.0...v19.1.1

v19.1.0

Compare Source

What's Changed

Full Changelog: raineorshine/npm-check-updates@v19.0.0...v19.1.0

v19.0.0

Compare Source

Breaking
  • node >= 20 required
  • --workspaces (plural) short option -ws changed to -w
    • Better compatibility with commander v13
    • Short option should always be a single character for consistency
    • Replaces the short option for --workspace (singular)
    • --workspace (singular) no longer has a short option.

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.1

Compare Source

v18.2.0

Compare Source

Thanks to community members for raising awareness and to @​SebastianSedzik for the implementation.

See: #​1547

Feature: --cooldown

Usage:

ncu --cooldown [n]
ncu -c [n]

The cooldown option helps protect against supply chain attacks by requiring package versions to be published at least the given number of days before considering them for upgrade.

Note that previous stable versions will not be suggested. The package will be completely ignored if its latest published version is within the cooldown period. This is due to a limitation of the npm registry, which does not provide a way to query previous stable versions.

Example:

Let's examine how cooldown works with a package that has these versions available:

1.0.0          Released 7 days ago    (initial version)
1.1.0          Released 6 days ago    (minor update)
1.1.1          Released 5 days ago    (patch update)
1.2.0          Released 5 days ago    (minor update)
2.0.0-beta.1   Released 5 days ago    (beta release)
1.2.1          Released 4 days ago    (patch update)
1.3.0          Released 4 days ago    (minor update) [latest]
2.0.0-beta.2   Released 3 days ago    (beta release)
2.0.0-beta.3   Released 2 days ago    (beta release) [beta]

With default target (latest):

$ ncu --cooldown 5

No update will be suggested because:

  • Latest version (1.3.0) is only 4 days old.
  • Cooldown requires versions to be at least 5 days old
  • Use --cooldown 4 or lower to allow this update

With @beta/@tag target:

$ ncu --cooldown 3 --target @​beta

No update will be suggested because:

  • Current beta (2.0.0-beta.3) is only 2 days old
  • Cooldown requires versions to be at least 3 days old
  • Use --cooldown 2 or lower to allow this update

With other targets:

$ ncu --cooldown 5 --target greatest|newest|minor|patch|semver

Each target will select the best version that is at least 5 days old:

greatest → 1.2.0        (highest version number outside cooldown)
newest   → 2.0.0-beta.1 (most recently published version outside cooldown)
minor    → 1.2.0        (highest minor version outside cooldown)
patch    → 1.1.1        (highest patch version outside cooldown)

Note for latest/tag targets:

⚠️ For packages that update frequently (e.g. daily releases), using a long cooldown period (7+ days) with the default --target latest or --target @​tag may prevent all updates since new versions will be published before older ones meet the cooldown requirement. Please consider this when setting your cooldown period.

v18.1.1

Compare Source

v18.1.0

Compare Source

v18.0.3

Compare Source

v18.0.2

Compare Source

v18.0.1

Compare Source

v18.0.0

Compare Source

Breaking

The only breaking change in v18 is with the -g/--global flag.

npm-check-updates -g will now auto-detect your package manager based on the execution path. Previously, it defaulted to npm.

  • yarn dlx ncu -g --packageManager yarnyarn dlx ncu -g
  • pnpm dlx ncu --global --packageManager pnpmpnpm dlx ncu -g
  • bunx ncu -g--packageManager pnpmbunx ncu -g

If for some reason you were running ncu -g with an alternative package manager and relying on it checking the global npm packages, you will need to now explicitly specify npm:

  • ncu -gncu -g--packageManager npm

Thanks to @​LuisFerLCC for the improvement (#​1514).

raineorshine/npm-check-updates@v17.1.18...v18.0.0

v17.1.18

Compare Source

Breaking

The only breaking change in v18 is with the -g/--global flag.

npm-check-updates -g will now auto-detect your package manager based on the execution path. Previously, it defaulted to npm.

  • yarn dlx ncu -g --packageManager yarnyarn dlx ncu -g
  • pnpm dlx ncu --global --packageManager pnpmpnpm dlx ncu -g
  • bunx ncu -g--packageManager pnpmbunx ncu -g

If for some reason you were running ncu -g with an alternative package manager and relying on it checking the global npm packages, you will need to now explicitly specify npm:

  • ncu -gncu -g--packageManager npm

Thanks to @​LuisFerLCC for the improvement (#​1514).

raineorshine/npm-check-updates@v17.1.18...v18.0.0

v17.1.17

Compare Source

v17.1.16

Compare Source

v17.1.15

Compare Source

v17.1.14

Compare Source

v17.1.13

Compare Source

v17.1.12

Compare Source

v17.1.11

Compare Source

v17.1.10

Compare Source

v17.1.9

Compare Source

v17.1.8

Compare Source

v17.1.7

Compare Source

v17.1.6

Compare Source

v17.1.5

Compare Source

v17.1.4

Compare Source

v17.1.3

Compare Source

v17.1.2

Compare Source

v17.1.1

Compare Source

Breaking

The only breaking change in v18 is with the -g/--global flag.

npm-check-updates -g will now auto-detect your package manager based on the execution path. Previously, it defaulted to npm.

  • yarn dlx ncu -g --packageManager yarnyarn dlx ncu -g
  • pnpm dlx ncu --global --packageManager pnpmpnpm dlx ncu -g
  • bunx ncu -g--packageManager pnpmbunx ncu -g

If for some reason you were running ncu -g with an alternative package manager and relying on it checking the global npm packages, you will need to now explicitly specify npm:

  • ncu -gncu -g--packageManager npm

Thanks to @​LuisFerLCC for the improvement (#​1514).

raineorshine/npm-check-updates@v17.1.18...v18.0.0

v17.1.0

Compare Source

v17.0.6

Compare Source

v17.0.5

Compare Source

v17.0.4

Compare Source

v17.0.3

Compare Source

v17.0.2

Compare Source

v17.0.1

Compare Source

v17.0.0

Compare Source

Breaking
  • Require node >= 18.18.0
  • Deprecated versions are no longer excluded by default, as it requires fetching package info for every published version, significantly slowing down upgrades.
    • You can opt in with --no-deprecated in the CLI or deprecated: false in your ncurc config.
  • In workspaces mode, --root is now set by default (#​1353)
    • To not check the root package.json, use --no-root.
  • If you have a packageManager field in your package.json, it is now upgraded by default (#​1390)
    • Use --dep prod,dev,optional for the old behavior.

raineorshine/npm-check-updates@v16.14.20...v17.0.0

v16.14.20

Compare Source

Breaking
  • Require node >= 18.18.0
  • Deprecated versions are no longer excluded by default, as it requires fetching package info for every published version, significantly slowing down upgrades.
    • You can opt in with --no-deprecated in the CLI or deprecated: false in your ncurc config.
  • In workspaces mode, --root is now set by default (#​1353)
    • To not check the root package.json, use --no-root.
  • If you have a packageManager field in your package.json, it is now upgraded by default (#​1390)
    • Use --dep prod,dev,optional for the old behavior.

raineorshine/npm-check-updates@v16.14.20...v17.0.0

v16.14.19

Compare Source

v16.14.18

Compare Source

v16.14.17

Compare Source

v16.14.16

Compare Source

v16.14.15

Compare Source

v16.14.14

Compare Source

v16.14.13

Compare Source

v16.14.12

Compare Source

v16.14.11

Compare Source

v16.14.10

Compare Source

v16.14.9

Compare Source

v16.14.8

Compare Source

v16.14.7

Compare Source

v16.14.6

Compare Source

v16.14.5

Compare Source

v16.14.4

Compare Source

v16.14.3

Compare Source

v16.14.2

Compare Source

Breaking
  • Require node >= 18.18.0
  • Deprecated versions are no longer excluded by default, as it requires fetching package info for every published version, significantly slowing down upgrades.
    • You can opt in with --no-deprecated in the CLI or deprecated: false in your ncurc config.
  • In workspaces mode, --root is now set by default (#​1353)
    • To not check the root package.json, use --no-root.
  • If you have a packageManager field in your package.json, it is now upgraded by default (#​1390)
    • Use --dep prod,dev,optional for the old behavior.

raineorshine/npm-check-updates@v16.14.20...v17.0.0

v16.14.1

Compare Source

v16.14.0

Compare Source

bun

Feature
  • Added experimental support for bun package manager.
  • Automatically used if bun.lockb is detected.
  • Assistance needed to test it out on different platforms.
$ ncu --packageManager bun
$ ncu -p bun

Thanks to @​ImBIOS for the PR!

v16.13.4

Compare Source

v16.13.3

Compare Source

v16.13.2

Compare Source

v16.13.1

Compare Source

v16.13.0

Compare Source

Feature
  • Added --install option to control auto-install behavior.

Usage:

ncu --install [value]

Default: prompt

Control the auto-install behavior.

alwaysRuns your package manager's install command automatically after upgrading.
neverDoes not install and does not prompt.
promptShows a message after upgrading that recommends an install, but does not install. In interactive mode, prompts for install. (default)

v16.12.3

Compare Source

v16.12.2

Compare Source

v16.12.1

Compare Source

v16.12.0

Compare Source

v16.11.2

Compare Source

v16.11.1

Compare Source

v16.11.0

Compare Source

v16.10.19

Compare Source

v16.10.18

Compare Source

v16.10.17

Compare Source

v16.10.16

Compare Source

v16.10.15

Compare Source

v16.10.14

Compare Source

v16.10.13

Compare Source

v16.10.12

Compare Source

v16.10.11

Compare Source

v16.10.10

Compare Source

v16.10.9

Compare Source

v16.10.8

Compare Source

v16.10.7

Compare Source

v16.10.6

Compare Source

v16.10.5

Compare Source

v16.10.4

Compare Source

v16.10.3

Compare Source

v16.10.2

Compare Source

v16.10.1

Compare Source

v16.10.0

Compare Source

Feature

  • Added filterResults option to filter out upgrades based on a user provided function.

filterResults runs after new versions are fetched, in contrast to filter and filterVersion, which run before. This allows you to filter out upgrades with filterResults based on how the version has changed (e.g. a major version change).

Only available in .ncurc.js or when importing npm-check-updates as a module.

/** Filter out non-major version updates.
  @​param {string} packageName               The name of the dependency.
  @​param {string} currentVersion            Current version declaration (may be range).
  @​param {SemVer[]} currentVersionSemver    Current version declaration in semantic versioning format (may be range).
  @​param {string} upgradedVersion           Upgraded version.
  @​param {SemVer} upgradedVersionSemver     Upgraded version in semantic versioning format.
  @​returns {boolean}                        Return true if the upgrade should be kept, otherwise it will be ignored.
*/
filterResults: (packageName, {currentVersion, currentVersionSemver, upgradedVersion, upgradedVersionSemver}) => {
  const currentMajorVersion = currentVersionSemver?.[0]?.major
  const upgradedMajorVersion = upgradedVersionSemver?.major
  if (currentMajorVersion && upgradedMajorVersion) {
    return currentMajorVersion < upgradedMajorVersion
  }
  return true
}

For the SemVer type definition, see: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring

Thanks to mslowiak for this enhancement!

v16.9.0

Compare Source

v16.8.2

Compare Source

v16.8.1

Compare Source

v16.8.0

Compare Source

Feature

  • Added --format lines
$ ncu --format lines
@&#8203;ava/typescript@^4.0.0
ava@^5.2.0
eslint@^8.36.0
lerna@^6.5.1
typescript@^5.0.2

This is particularly useful for upgrading global modules:

npm install -g $(ncu -g --format lines)

Thanks to @​vanodevium for the PR!

v16.7.13

Compare Source

v16.7.12

Compare Source

v16.7.11

Compare Source

v16.7.10

Compare Source

v16.7.9

Compare Source

v16.7.8

Compare Source

v16.7.7

Compare Source

v16.7.6

Compare Source

v16.7.5

Compare Source

v16.7.4

Compare Source

v16.7.3

Compare Source

v16.7.2

Compare Source

v16.7.1

Compare Source

v16.7.0

Compare Source

v16.6.5

Compare Source

v16.6.4

Compare Source

v16.6.3

Compare Source

v16.6.2

Compare Source

v16.6.1

Compare Source

v16.6.0

Compare Source

atom-community/prettier-config-atomic (prettier-config-atomic)

v4.0.0

Compare Source

What's Changed

Breaking Change

The config now supports Prettier v3.0 only. The code itself is an ESM module, so use an import instead of require.

Full Changelog: atom-community/prettier-config-atomic@v3.1.0...v4.0.0

v3.1.0

Compare Source

Bug Fixes
Features

3.0.11 (2022-07-03)

Bug Fixes

3.0.10 (2022-06-22)

Bug Fixes
  • deps: update dependency prettier to v2.7.1 (2825b26)

3.0.9 (2022-04-02)

Bug Fixes
  • deps: update dependency prettier to v2.6.2 (a55d98d)

3.0.8 (2022-03-26)

Bug Fixes
  • deps: update dependency prettier to v2.6.1 (c4f041c)

3.0.7 (2022-03-17)

Bug Fixes
  • update prettier and dependencies (f03379b)

3.0.6 (2022-03-13)

Reverts
  • Revert "fix(deps): update dependency prettier to v2.5.1" (2589e78)

3.0.5 (2022-03-12)

Bug Fixes
  • deps: update dependency prettier to v2.5.1 (f6a291e)

3.0.4 (2022-03-11)

Bug Fixes

3.0.3 (2022-01-27)

Bug Fixes

3.0.2 (2022-01-27)

Bug Fixes

3.0.1 (2021-10-02)

Bug Fixes
  • inline the plugin into a function (9ed6476)

v3.0.10

Compare Source

Bug Fixes
Features

3.0.11 (2022-07-03)

Bug Fixes

3.0.10 (2022-06-22)

Bug Fixes
  • deps: update dependency prettier to v2.7.1 (2825b26)

3.0.9 (2022-04-02)

Bug Fixes
  • deps: update dependency prettier to v2.6.2 (a55d98d)

3.0.8 (2022-03-26)

Bug Fixes
  • deps: update dependency prettier to v2.6.1 (c4f041c)

3.0.7 (2022-03-17)

Bug Fixes
  • update prettier and dependencies (f03379b)

3.0.6 (2022-03-13)

Reverts
  • Revert "fix(deps): update dependency prettier to v2.5.1" (2589e78)

3.0.5 (2022-03-12)

Bug Fixes
  • deps: update dependency prettier to v2.5.1 (f6a291e)

3.0.4 (2022-03-11)

Bug Fixes

3.0.3 (2022-01-27)

Bug Fixes

3.0.2 (2022-01-27)

Bug Fixes

3.0.1 (2021-10-02)

Bug Fixes
  • inline the plugin into a function (9ed6476)

v3.0.9

Compare Source

Bug Fixes
Features

3.0.11 (2022-07-03)

Bug Fixes

3.0.10 (2022-06-22)

Bug Fixes
  • deps: update dependency prettier to v2.7.1 (2825b26)

3.0.9 (2022-04-02)

Bug Fixes
  • deps: update dependency pr

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update dependency npm-check-updates to v16.6.0 Update dependency npm-check-updates to v16.6.0 Dec 17, 2022
@renovate renovate bot changed the title Update dependency npm-check-updates to v16.6.0 chore(deps): update dependency npm-check-updates to v16.6.0 Dec 17, 2022
@renovate renovate bot force-pushed the renovate/devdependencies branch from 982e318 to b7b4e52 Compare December 21, 2022 21:15
@renovate renovate bot changed the title chore(deps): update dependency npm-check-updates to v16.6.0 chore(deps): update dependency npm-check-updates to v16.6.2 Dec 21, 2022
@renovate renovate bot force-pushed the renovate/devdependencies branch from b7b4e52 to 1f6ada0 Compare January 23, 2023 18:35
@renovate renovate bot changed the title chore(deps): update dependency npm-check-updates to v16.6.2 chore(deps): update dependency npm-check-updates to v16.6.3 Jan 23, 2023
@renovate renovate bot changed the title chore(deps): update dependency npm-check-updates to v16.6.3 chore(deps): update dependency npm-check-updates to v16.6.4 Feb 5, 2023
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from ba7d550 to 087cecb Compare February 6, 2023 17:52
@renovate renovate bot changed the title chore(deps): update dependency npm-check-updates to v16.6.4 chore(deps): update dependency npm-check-updates to v16.6.5 Feb 6, 2023
@renovate renovate bot changed the title chore(deps): update dependency npm-check-updates to v16.6.5 chore(deps): update dependency npm-check-updates to v16.7.2 Feb 9, 2023
@renovate renovate bot force-pushed the renovate/devdependencies branch from 087cecb to 9749386 Compare February 9, 2023 19:22
@renovate renovate bot force-pushed the renovate/devdependencies branch from 9749386 to b6e73ef Compare March 17, 2023 22:07
@renovate renovate bot changed the title chore(deps): update dependency npm-check-updates to v16.7.2 chore(deps): update devdependencies Mar 17, 2023
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from f4ad513 to 4999021 Compare March 22, 2023 21:14
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from 7423e83 to 832f154 Compare April 3, 2023 11:23
@renovate renovate bot force-pushed the renovate/devdependencies branch from 832f154 to ff3539e Compare April 17, 2023 12:16
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from bea682b to a62f03c Compare June 1, 2023 19:56
@renovate renovate bot force-pushed the renovate/devdependencies branch from a62f03c to f33fd8b Compare June 4, 2023 14:42
@renovate renovate bot force-pushed the renovate/devdependencies branch 3 times, most recently from 0aae332 to 79f4071 Compare June 19, 2023 09:47
@renovate renovate bot force-pushed the renovate/devdependencies branch 3 times, most recently from 977d7f8 to 17127ed Compare June 29, 2023 02:51
@renovate renovate bot force-pushed the renovate/devdependencies branch from 17127ed to 6d2ae23 Compare July 6, 2023 11:29
@renovate renovate bot force-pushed the renovate/devdependencies branch 4 times, most recently from c051505 to 0633afe Compare August 22, 2023 18:57
@renovate renovate bot force-pushed the renovate/devdependencies branch 3 times, most recently from c87b438 to feb2c8b Compare August 28, 2023 17:12
@renovate renovate bot force-pushed the renovate/devdependencies branch 4 times, most recently from a53da2c to 0e8613e Compare September 13, 2023 17:20
@renovate renovate bot force-pushed the renovate/devdependencies branch 3 times, most recently from b2b237a to 26f1439 Compare September 19, 2023 14:57
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from f7e8959 to 20e06fa Compare September 28, 2023 12:52
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from 6271a93 to 5d83f7e Compare October 9, 2023 08:30
@renovate renovate bot force-pushed the renovate/devdependencies branch 3 times, most recently from c17ab3d to b377c4a Compare October 19, 2023 16:52
@renovate renovate bot force-pushed the renovate/devdependencies branch from b377c4a to 618e16d Compare October 23, 2023 12:29
@renovate
Copy link
Contributor Author

renovate bot commented Nov 6, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
 WARN  The "store" setting has been renamed to "store-dir". Please use the new name.
 WARN  GET https://registry.npmjs.org/assemblyscript error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/prettier-config-atomic error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/typescript error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@babel%2Fcore error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/coffeescript error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-babel/-/plugin-babel-5.3.1.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-commonjs/-/plugin-commonjs-22.0.2.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-json/-/plugin-json-4.1.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-node-resolve/-/plugin-node-resolve-13.3.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-replace/-/plugin-replace-4.0.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-typescript/-/plugin-typescript-8.4.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-wasm/-/plugin-wasm-5.1.2.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/array-includes-any/-/array-includes-any-2.7.3.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/csso-cli/-/csso-cli-4.0.1.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/rollup/-/rollup-2.42.1.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/npm-check-updates error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/assemblyscript error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/prettier-config-atomic error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/typescript error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@babel%2Fcore error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/coffeescript error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-babel/-/plugin-babel-5.3.1.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-commonjs/-/plugin-commonjs-22.0.2.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-json/-/plugin-json-4.1.0.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-node-resolve/-/plugin-node-resolve-13.3.0.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-replace/-/plugin-replace-4.0.0.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-typescript/-/plugin-typescript-8.4.0.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/@rollup/plugin-wasm/-/plugin-wasm-5.1.2.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/array-includes-any/-/array-includes-any-2.7.3.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/csso-cli/-/csso-cli-4.0.1.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/rollup/-/rollup-2.42.1.tgz error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/npm-check-updates error (ERR_INVALID_THIS). Will retry in 1 minute. 1 retries left.
 WARN  GET https://registry.npmjs.org/rollup-plugin-assemblyscript/-/rollup-plugin-assemblyscript-2.0.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 ERR_INVALID_THIS  Value of "this" must be of type URLSearchParams
 WARN  GET https://registry.npmjs.org/rollup-plugin-auto-external/-/rollup-plugin-auto-external-2.0.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/rollup-plugin-coffee-script/-/rollup-plugin-coffee-script-2.0.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/rollup-plugin-css-only/-/rollup-plugin-css-only-3.1.0.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/rollup-plugin-execute/-/rollup-plugin-execute-1.1.1.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/rollup-plugin-terser/-/rollup-plugin-terser-7.0.2.tgz error (ERR_INVALID_THIS). Will retry in 10 seconds. 2 retries left.

@renovate renovate bot force-pushed the renovate/devdependencies branch from 618e16d to 500063a Compare November 6, 2023 06:27
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from 1d23caf to 9415b7a Compare November 19, 2023 22:10
@renovate renovate bot force-pushed the renovate/devdependencies branch from 9415b7a to e524392 Compare December 13, 2023 18:14
@renovate renovate bot force-pushed the renovate/devdependencies branch from e524392 to 3b0e12f Compare January 11, 2024 10:27
@renovate
Copy link
Contributor Author

renovate bot commented Jul 31, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
(node:1192) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants