Build(deps-dev): Bump @angular-eslint/builder from 17.5.1 to 18.0.1 in /angular
Bumps @angular-eslint/builder from 17.5.1 to 18.0.1.
Release notes
Sourced from @angular-eslint/builder
's releases.
v18.0.1
18.0.1 (2024-05-30)
🩹 Fixes
- move typescript-eslint packages to peerDeps, consistently allow v7 and v8 (#1856)
As part of the v18 release, support for typescript-eslint v8 prereleases was added. For authors of custom rules that consume the
@angular-eslint/utils
or new@angular-eslint/test-utils
packages, the initial way this was set up with dependencies could cause type conflicts between v7 and v8. To resolve this the@angular-eslint/*
packages now depend on@typescript-eslint/*
packages via a peerDependency which permits both v7 and v8 prereleases.
❤ ️ Thank You
- James Henry
@JamesHenry
v18.0.0
18.0.0 (2024-05-29)
As always we recommend that you update your existing workspaces by using
ng update
as we provide some helpful schematics to help migrate your workspaces to the latest and greatest. Running the following will update Angular, the Angular CLI and angular-eslint together:ng update @angular/core @angular/cli @angular-eslint/schematics
NOTE: There will not be any migration of your setup to ESLint v9 or flat configs for existing workspaces in v18.
The ESLint team are working on auto-migrate tooling which we will leverage in an opt-in conversion generator once it is ready in a v18 minor release and consider full auto-migration in v19 in six months (aligned with Angular major release schedule as always).
If you want to manually migrate your workspace to use ESLint v9,
typescript-eslint
v8, and flat config you are welcome to and it should be fully supported in v18.If you are going to attempt this, we strongly recommended creating a fresh Angular v18 workspace and adding angular-eslint to it per the instructions below and then copying the dependencies and configs that it applies into your existing workspace
Here is an example of what the new flat config with
angular-eslint
v18,typescript-eslint
v8, and ESLint v9 looks like:
Adding to New Angular Workspaces in v18
There is a decision to be made when adding to new Angular v18 workspaces.
Just as before, if you want to add
angular-eslint
to a workspace with no existing lint setup, you leverageng add
with the@angular-eslint/schematics
package.The difference is in v18, you have the option of using either:
- the latest version of ESLint v9, with the latest default so called "flat config" (
eslint.config.js
) alongside the latest prerelease oftypescript-eslint
v8 (https://typescript-eslint.io/blog/announcing-typescript-eslint-v8-beta) OR- the final stable version of ESLint v8, with the legacy so called "eslintrc" config (
.eslintrc.json
) and the latest stable version oftypescript-eslint
v7The ESLint v9 option is the default scenario if you simply run
ng add
with no other changes. If you want to signal toangular-eslint
that you instead want to go with the ESLint v8 option, simply add aneslint
v8 (the exact version does not matter, it just needs to be less than 9)devDependency
in your package.json before running theng add
. That's it - you don't even need to install theeslint
package, it just needs to be listed there.
... (truncated)
Changelog
Sourced from @angular-eslint/builder
's changelog.
18.0.1 (2024-05-30)
🩹 Fixes
- move typescript-eslint packages to peerDeps, consistently allow v7 and v8
❤ ️ Thank You
- James Henry
18.0.0 (2024-05-29)
🚀 Features
⚠ ️ angular-eslint v18
⚠ ️ Breaking Changes
⚠ ️ angular-eslint v18
❤ ️ Thank You
- James Henry
17.5.2 (2024-05-28)
🩹 Fixes
- update typescript-eslint packages to v7.11.0
Commits
-
f36d027
chore(release): publish 18.0.1 -
fd69e8e
fix: move typescript-eslint packages to peerDeps, consistently allow v7 and v... -
c8dff2f
chore(release): publish 18.0.0 -
7c84ab7
feat!: angular-eslint v18 (#1830) -
05e8cf9
chore(release): publish 17.5.2 -
b2b0700
fix: update typescript-eslint packages to v7.11.0 (#1846) - See full diff in compare view
Dependabot commands
You can trigger Dependabot actions by commenting on this MR
-
$dependabot recreate
will recreate this MR rewriting all the manual changes and resolving conflicts