chore(deps): update devdependencies by renovate[bot] · Pull Request #40 · atom-community/atom-ide-template

renovate · 2021-09-04T01:14:12Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/atom (source)	`1.40.11` -> `1.40.14`
@types/jasmine (source)	`^3.8.2` -> `^5.0.0`
@types/node (source)	`^16.6.0` -> `^20.0.0`
atom-jasmine3-test-runner	`5.2.7` -> `5.2.13`
eslint-config-atomic	`1.16.2` -> `1.20.5`
npm-check-updates	`11.8.3` -> `16.14.6`
prettier-config-atomic	`^2.0.5` -> `^3.0.0`
shx	`0.3.3` -> `0.3.4`
terser-config-atomic	`^0.1.1` -> `^1.0.0`
typescript (source)	`^4.3.5` -> `^5.0.0`

Release Notes

UziTech/atom-jasmine3-test-runner (atom-jasmine3-test-runner)

`v5.2.13`

Compare Source

Bug Fixes

deps: update dependency glob to ^8.0.2 (ba8f133)

`v5.2.12`

Compare Source

Bug Fixes

deps: update dependency glob to v8 (cefa2f4)
fix glob path separator (392c3e9)

`v5.2.11`

Compare Source

Bug Fixes

deps: update dependency jasmine-local-storage to ^1.1.2 (f81b93c)
deps: update dependency jasmine2-focused to ^1.1.2 (ac9b251)

`v5.2.10`

Compare Source

Bug Fixes

deps: update dependency jasmine-unspy to ^1.1.2 (5e46655)

`v5.2.9`

Compare Source

Bug Fixes

deps: update dependency jasmine to ~3.10.0 (#297) (1286ce9)

`v5.2.8`

Compare Source

Bug Fixes

deps: update dependency jasmine to ~3.9.0 (579672f)

atom-ide-community/eslint-config-atomic (eslint-config-atomic)

Full Changelog: atom-community/eslint-config-atomic@v1.19.2...v1.19.3
fix: ignore node_modules even if not in gitignore

`v1.19.2`

Compare Source

What's Changed

fix: turn off no-unused-vars for TypeScript by @aminya in https://github.com/atom-community/eslint-config-atomic/pull/72
fix: only warn on project-based rules in case there is a TypeScript file by @aminya in https://github.com/atom-community/eslint-config-atomic/pull/72

Full Changelog: atom-community/eslint-config-atomic@v1.19.1...v1.19.2

`v1.19.1`

Compare Source

What's Changed

fix: remove no-parameter-properties by @aminya in https://github.com/atom-community/eslint-config-atomic/pull/71

Full Changelog: atom-community/eslint-config-atomic@v1.19.0...v1.19.1

`v1.19.0`

Compare Source

What's Changed

feat: add ignore patterns for no-unused-vars + update dependencies by @aminya in https://github.com/atom-community/eslint-config-atomic/pull/69
feat: auto-disable project based rules for TypeScript it tsconfig is not found by @aminya in https://github.com/atom-community/eslint-config-atomic/pull/70

Full Changelog: atom-community/eslint-config-atomic@v1.18.3...v1.19.0

`v1.18.3`

Compare Source

What's Changed

fix(deps): update dependencies

Full Changelog: atom-community/eslint-config-atomic@v1.18.2...v1.18.3

`v1.18.2`

Compare Source

What's Changed

fix: update dependencies by @aminya in https://github.com/atom-community/eslint-config-atomic/pull/67

Full Changelog: atom-community/eslint-config-atomic@v1.18.1...v1.18.2

`v1.18.1`

Compare Source

Bug Fixes

add one-var to the rules (4983c1f) and (aa8dfa9)

`v1.18.0`

Compare Source

Bug Fixes

set strict-peer-dependencies=false (42dfc86)
update dependencies (f057f0c)

Features

support eslint 8 by excluding coffee if the version is >=8 (1a2ecce)
update the bundles eslint to 8 (e570c21)

`v1.17.1`

Compare Source

Bug Fixes

update dependencies (d88aa50)

`v1.17.0`

Compare Source

Bug Fixes

update dependencies (0e6b15b)

Features

make coffee plugin optional (2915bc4)

`v1.16.6`

Compare Source

Bug Fixes

update dependencies (e019f0b)

`v1.16.5`

Compare Source

Bug Fixes

update dependencies (5b34ed7)

`v1.16.4`

Compare Source

Bug Fixes

update dependencies (0acbce0)

`v1.16.3`

Compare Source

Bug Fixes

update dependencies (bf1d8f8)

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

`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

`v16.14.1`

Compare Source

`v16.14.0`

Compare Source

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.

always	Runs your package manager's install command automatically after upgrading.
never	Does not install and does not prompt.
prompt	Shows 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.
  @&#8203;param {string} packageName               The name of the dependency.
  @&#8203;param {string} currentVersion            Current version declaration (may be range).
  @&#8203;param {SemVer[]} currentVersionSemver    Current version declaration in semantic versioning format (may be range).
  @&#8203;param {string} upgradedVersion           Upgraded version.
  @&#8203;param {SemVer} upgradedVersionSemver     Upgraded version in semantic versioning format.
  @&#8203;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

`v16.5.6`

Compare Source

`v16.5.5`

Compare Source

`v16.5.4`

Compare Source

`v16.5.3`

Compare Source

`v16.5.2`

Compare Source

`v16.5.1`

Compare Source

`v16.5.0`

Compare Source

`v16.4.3`

Compare Source

`v16.4.2`

Compare Source

`v16.4.1`

Compare Source

`v16.4.0`

Compare Source

Feature

Added --cacheClear option for—you guessed it—clearing the cache 🫥.

This brings the suite of cache-related options to:

--cache : Cache versions to the cache file.
--cacheClear : Clear the default cache, or the cache file specified by --cacheFile.
--cacheExpiration <min> : Cache expiration in minutes (default: 10).
--cacheFile <path> : Filepath for the cache file (default: "~/.ncu-cache.json").

Thanks to @ly3xqhl8g9 whose code is gratefully more lucid than his username.

`v16.3.25`

Compare Source

`v16.3.24`

Compare Source

`v16.3.23`

Compare Source

`v16.3.22`

Compare Source

`v16.3.21`

Compare Source

`v16.3.20`

Compare Source

`v16.3.19`

Compare Source

`v16.3.18`

Compare Source

`v16.3.17`

Compare Source

`v16.3.16`

Compare Source

`v16.3.15`

Compare Source

`v16.3.14`

Compare Source

`v16.3.13`

Compare Source

`v16.3.12`

Compare Source

`v16.3.11`

Compare Source

`v16.3.10`

Compare Source

`v16.3.9`

Compare Source

`v16.3.8`

Compare Source

`v16.3.7`

Compare Source

`v16.3.6`

Compare Source

`v16.3.5`

Compare Source

`v16.3.4`

Compare Source

`v16.3.3`

Compare Source

`v16.3.2`

Compare Source

`v16.3.1`

Compare Source

`v16.3.0`

Compare Source

Feature

Added workspace support! 🚢

Upgrade all workspaces:

ncu --workspaces
ncu -ws

Upgrade a single workspace:

ncu --workspace a
ncu -w a

Upgrade more than one workspace:

ncu --workspace a --workspace b
ncu -w a -w b

Upgrade all workspaces AND the root project:

ncu --workspaces --root

Upgrade a single workspace AND the root project:

ncu --workspace a --root

Notes

If workspaces or --workspace is run in --interactive mode, ncu will prompt to npm install once in the root project rather than separately in each workspace (#1182).
Running --deep will not trigger workspace support.

`v16.2.1`

Compare Source

`v16.2.0`

Compare Source

`v16.1.3`

Compare Source

`v16.1.2`

Compare Source

`v16.1.1`

Compare Source

`v16.1.0`

Compare Source

`v16.0.6`

Compare Source

`v16.0.5`

Compare Source

`v16.0.4`

Compare Source

`v16.0.3`

Compare Source

`v16.0.2`

Compare Source

`v16.0.1`

Compare Source

`v16.0.0`

Compare Source

Breaking

Automatic detection of package data on stdin has been removed. This feature was deprecated in v14.0.0. Add --stdin for old behavior.
Wild card filters now apply to scoped packages. Previously, ncu -f '*vite*' would not include @vitejs/plugin-react. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior.

raineorshine/npm-check-updates@v15.3.4...v16.0.0

`v15.3.4`

Compare Source

`v15.3.3`

Compare Source

`v15.3.2`

Compare Source

`v15.3.1`

Compare Source

`v15.3.0`

Compare Source

`v15.2.6`

Compare Source

`v15.2.5`

Compare Source

`v15.2.4`

Compare Source

`v15.2.3`

Compare Source

`v15.2.2`

Compare Source

`v15.2.1`

Compare Source

`v15.2.0`

Compare Source

`v15.1.0`

Compare Source

`v15.0.5`

Compare Source

`v15.0.4`

Compare Source

`v15.0.3`

Compare Source

`v15.0.2`

Compare Source

`v15.0.1`

Compare Source

`v15.0.0`

Compare Source

Breaking

node >= 14.14 is now required (#1145)
- Needed to upgrade update-notifier with has a moderate severity vulnerability
yarn autodetect has been improved (#1148)
- This is a patch, though technically it is breaking. In the obscure case where --packageManager is not given, there is no package-lock.json in the current folder, and there is a yarn.lock in an ancestor directory, npm-check-updates will now use yarn.
- More practically, if you needed to specify --packageManager yarn explicitly before, you may not have to now

raineorshine/npm-check-updates@v14.1.1...v15.0.0

`v14.1.1`

Compare Source

`v14.1.0`

Compare Source

Features

Group

You can now group upgrades by risk level using --format group:

Interactive Mode

Interactive mode was completely rewritten for a better user experience.

Inspired by npm-check.

Combine with --format group for a truly luxe experience:

Static Registry

A new option --packageManager staticRegistry allows upgrades to be recommended from a static JSON file. This can be used to power custom versioning infrastructure that is completely independent from the npm registry.

Thanks to agrouse who did a fine job on the PR.

Example:

$ ncu --packageManager staticRegistry --registry ./my-registry.json

my-registry.json:

{
  "prettier": "2.7.0",
  "typescript": "4.7.0"
}

The latest versions of prettier and typescript are set in the registry file. When ncu is run, it will recommend upgrades from the static registry file without touching the npm registry:

$ ncu --packageManager staticRegistry --registry ./my-registry.json
Checking /Users/raine/projects/ncu-issues/14.1.0/package.json
[====================] 2/2 100%

 prettier    ^2.0.1  →  ^2.7.0
 typescript  ^3.4.0  →  ^4.7.0

Run ncu -u to upgrade package.json

`v14.0.2`

Compare Source

`v14.0.1`

Compare Source

`v14.0.0`

Compare Source

Breaking

Prerelease versions are now "upgraded" to versions with a different preid.

For example, if you have a dependency at 1.3.3-next.1 and the version fetched by ncu is 1.2.3-dev.2, ncu will suggest an "upgrade" to 1.2.3-dev.2. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.

Since this change affects only prereleases, there is no impact on default ncu usage that fetches the latest version. With --pre 1 or --target newest or --target greatest, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new --target @[tag] feature.

If you have a use case where this change is not what is desired, please report an issue. The intention is for zero disruption to current usage.

Features

You can now upgrade to a specific tag, e.g. --target @next. Thanks to IMalyugin.

raineorshine/npm-check-updates@v13.1.5...v14.0.0

`v13.1.5`

Compare Source

`v13.1.4`

Compare Source

`v13.1.3`

Compare Source

`v13.1.2`

Compare Source

`v13.1.1`

Compare Source

`v13.1.0`

Compare Source

`v13.0.4`

Compare Source

`v13.0.3`

Compare Source

`v13.0.2`

Compare Source

`v13.0.1`

Compare Source

`v13.0.0`

Compare Source

Breaking

node >= 14 is now required
Several options which have long been deprecated have been removed:
- --greatest - Instead use --target greatest
- --newest - Instead use --target newest

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

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

This PR has been generated by Mend Renovate. View repository job log here.

renovate bot added the dependencies Pull requests that update a dependency file label Sep 4, 2021

renovate bot force-pushed the renovate/devdependencies branch from bda7e08 to a51282d Compare October 2, 2021 21:17

renovate bot changed the title ~~chore(deps): update dependency npm-check-updates to v11.8.5~~ chore(deps): update devdependencies Oct 2, 2021

renovate bot force-pushed the renovate/devdependencies branch from a51282d to 9208284 Compare March 7, 2022 14:37

renovate bot force-pushed the renovate/devdependencies branch from 9208284 to ef875fb Compare March 26, 2022 13:19

renovate bot force-pushed the renovate/devdependencies branch from ef875fb to 6c1afe8 Compare April 25, 2022 00:26

renovate bot force-pushed the renovate/devdependencies branch from 6c1afe8 to 9b7a6ce Compare May 15, 2022 20:31

renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from 62164fb to b80fa87 Compare June 23, 2022 20:35

renovate bot force-pushed the renovate/devdependencies branch from b80fa87 to 7c43b14 Compare September 25, 2022 18:30

renovate bot force-pushed the renovate/devdependencies branch from 7c43b14 to 292e532 Compare November 20, 2022 12:51

renovate bot force-pushed the renovate/devdependencies branch 3 times, most recently from 139dc8a to afe2fdc Compare March 22, 2023 20:39

renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from e541689 to 279858e Compare April 3, 2023 10:23

renovate bot force-pushed the renovate/devdependencies branch from 279858e to d197f7f Compare April 17, 2023 10:28

renovate bot force-pushed the renovate/devdependencies branch 4 times, most recently from 37ded18 to bc328c7 Compare June 1, 2023 18:26

renovate bot force-pushed the renovate/devdependencies branch 3 times, most recently from 69194a5 to f413aa7 Compare June 10, 2023 22:03

renovate bot force-pushed the renovate/devdependencies branch 6 times, most recently from 3171547 to 6d74ca2 Compare June 19, 2023 18:42

renovate bot force-pushed the renovate/devdependencies branch 7 times, most recently from b738cef to 5ad1641 Compare September 20, 2023 04:20

renovate bot force-pushed the renovate/devdependencies branch 7 times, most recently from 3e4518b to e789b4d Compare September 29, 2023 19:06

renovate bot force-pushed the renovate/devdependencies branch 8 times, most recently from bbcdc6a to e6e0ae6 Compare October 7, 2023 00:29

renovate bot force-pushed the renovate/devdependencies branch 6 times, most recently from b9287fb to 55ff9ff Compare October 15, 2023 15:20

chore(deps): update devdependencies

d15f57e

renovate bot force-pushed the renovate/devdependencies branch from 55ff9ff to d15f57e Compare October 16, 2023 00:27

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update devdependencies#40

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

renovate bot commented Sep 4, 2021 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Sep 4, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Feature

Feature

Feature

Feature

Feature

renovate bot commented Sep 4, 2021 •

edited

Loading