chore(deps): update devdependencies #109

renovate · 2023-06-24T00:09:46Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-atomic	`1.18.1` -> `1.22.1`
npm-check-updates	`16.10.12` -> `19.1.2`
prettier-config-atomic	`^3.0.10` -> `^4.0.0`
typescript (source)	`5.0.2` -> `5.9.3`

Release Notes

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

`v1.22.1`

Compare Source

What's Changed

fix: do not fail on gitignore failures @aminya in atom-community#91
fix: optimize TypeScript project disable search by @aminya in atom-community#91

Full Changelog: atom-community/eslint-config-atomic@v1.22.0...v1.22.1

`v1.22.0`

Compare Source

What's Changed

fix: update dependencies by @aminya in atom-community#88

Full Changelog: atom-community/eslint-config-atomic@v1.21.2...v1.22.0

What's Changed

feat: add Solid-js by @aminya in atom-community#83
feat: add Astro Support by @aminya in atom-community#83
fix: Update dependencies by @aminya in atom-community#83

Full Changelog: atom-community/eslint-config-atomic@v1.20.6...v1.21.0

`v1.20.6`

Compare Source

What's Changed

fix: support mts/cts file extensions for TypeScript by @aminya in atom-community#82
fix: update dependencies @aminya in atom-community#82

Full Changelog: atom-community/eslint-config-atomic@v1.20.5...v1.20.6

`v1.20.5`

Compare Source

What's Changed

fix: handle undefined ignore in TypeScript rules by @aminya in atom-community#80

Full Changelog: atom-community/eslint-config-atomic@v1.20.4...v1.20.5

`v1.20.4`

Compare Source

What's Changed

fix: use cjs and specify commonjs type package by @aminya in atom-community#78

Full Changelog: atom-community/eslint-config-atomic@v1.20.1...v1.20.3

`v1.20.3`

Compare Source

`v1.20.2`

Compare Source

`v1.20.1`

Compare Source

What's Changed

feat: rewrite in TypeScript by @aminya in atom-community#77
fix: update dependencies by @aminya in atom-community#77

Full Changelog: atom-community/eslint-config-atomic@v1.19.3...v1.20.1

`v1.20.0`

Compare Source

`v1.19.3`

Compare Source

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 atom-community#72
fix: only warn on project-based rules in case there is a TypeScript file by @aminya in atom-community#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 atom-community#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 atom-community#69
feat: auto-disable project based rules for TypeScript it tsconfig is not found by @aminya in atom-community#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 atom-community#67

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

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

`v19.1.2`

Compare Source

What's Changed

fix: support singular 'catalog' field in pnpm-workspace.yaml by @afonsojramos in #1572

New Contributors

@afonsojramos made their first contribution in #1572

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

`v19.1.1`

Compare Source

What's Changed

fix(cooldown): handle CooldownFunction in config file by @SebastianSedzik in #1565

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

`v19.1.0`

Compare Source

What's Changed

feat(cooldown): support for cooldown predicate function by @SebastianSedzik in #1563

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 @&#8203;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 yarn → yarn dlx ncu -g
pnpm dlx ncu --global --packageManager pnpm → pnpm dlx ncu -g
bunx ncu -g--packageManager pnpm → bunx 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 -g → ncu -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 yarn → yarn dlx ncu -g
pnpm dlx ncu --global --packageManager pnpm → pnpm dlx ncu -g
bunx ncu -g--packageManager pnpm → bunx 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 -g → ncu -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 yarn → yarn dlx ncu -g
pnpm dlx ncu --global --packageManager pnpm → pnpm dlx ncu -g
bunx ncu -g--packageManager pnpm → bunx 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 -g → ncu -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

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

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

`v4.0.0`

Compare Source

What's Changed

feat: convert the config to ESM TypeScript by @aminya in #32

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

update dependencies (aa27598)

Features

support mdx (8af55b5)

3.0.11 (2022-07-03)

Bug Fixes

update dependencies (9fea372)

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

bump deps (659ac08)
require prettier-plugin-jsdoc (257495a)

3.0.3 (2022-01-27)

Bug Fixes

downgrade prettier (93fb612)

3.0.2 (2022-01-27)

Bug Fixes

update dependencies (c018a26)

3.0.1 (2021-10-02)

Bug Fixes

inline the plugin into a function (9ed6476)

microsoft/TypeScript (typescript)

`v5.9.3`: TypeScript 5.9.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

fixed issues query for Typescript 5.9.0 (Beta).
fixed issues query for Typescript 5.9.1 (RC).
No specific changes for TypeScript 5.9.2 (Stable)
fixed issues query for Typescript 5.9.3 (Stable).

Downloads are available on:

npm

`v5.9.2`: TypeScript 5.9

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

fixed issues query for Typescript 5.9.0 (Beta).
fixed issues query for Typescript 5.9.1 (RC).
No specific changes for TypeScript 5.9.2 (Stable)

Downloads are available on:

npm

`v5.8.3`: TypeScript 5.8.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement.

Downloads are available on:

npm

`v5.8.2`: TypeScript 5.8

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

npm

`v5.7.3`: TypeScript 5.7.3

Compare Source

For release notes, check out the release announcement.

Downloads are available on npm

`v5.7.2`: TypeScript 5.7

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

npm