You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran ng update to v9. Then I ran npm run lint. I received this error
▶npm run lint
> heroes-angular@0.0.0 lint /Users/papa/_git/heroes-angular
> ng lint
Linting "heroes-angular"...
no-use-before-declare is deprecated. Since TypeScript 2.9. Please use the built-in compiler checks instead.
All files pass linting.
It seems I had a legacy setting in tslint.json for "no-use-before-declare": true,
It would be great if the ng update removed any deprecated tslint settings.
The text was updated successfully, but these errors were encountered:
@mgechev, what is the current status of ESLint? If we're hoping to move towards that in the future, we'll need to decide how much support we want to give TSLint for the time being.
Since we'll still be support TSLint for the foreseeable future, we already need a migration to upgrade to TSLint 6.1. We can remove no-use-before-declare in that migration. This will need to be run manually in v9.x when it is ready, but will run automatically in v10 (assuming we don't migrate to ESLint by then).
In tslint version 6, several recommanded rules have been removed in the following PRs:
palantir/tslint#4871palantir/tslint#4312
With this migration we update the tslint depedency to 6+ and add back these rules in the user workspace `tslint.json` also we remove some deprecated rules.
Until version 10, this is an opt-in migration and users will need to run this manually with the below command:
```
ng update @angular/cli --migrate-only tslint-version-6
```
Closes: #17117
Reference: TOOL-1348
🐞 Bug report
Command (mark with an
x
)Description
I ran
ng update
to v9. Then I rannpm run lint
. I received this errorIt seems I had a legacy setting in
tslint.json
for"no-use-before-declare": true,
It would be great if the
ng update
removed any deprecated tslint settings.The text was updated successfully, but these errors were encountered: