-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: upgrade to eslint 6 #4933
Conversation
FIXME: Pending vuejs/eslint-plugin-vue#985 Need to remove the `resolutions` field in package.json before merging
if (config !== 'prettier') { | ||
// for any config other than `prettier`, | ||
// typescript ruleset should be appended to the end of the `extends` array | ||
eslintConfig.extends.push('@vue/typescript/recommended') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure whether we should use @vue/typescript/recommended
or @vue/typescript
here.
I gave it a basic look. Looks good. |
😅Finally, all the tests are passed! |
* feat: scaffold projects with eslint 6 * style: eslint fix * refactor: do not use hard-coded ecmaVersion, use babel-eslint for now * fix: upgrade to @vue/eslint-config-standard * style: continue fix lint errors * chore: upgrade to eslint-plugin-vue@^6.1.2 * refactor: use `ecmaVersion: 2020` for dynamic import syntax support * test: fix baseESLintConfig * chore: also update yarn.lock to fix CI caches * chore: update lockfile again, fix babel regressions * test: nightwatch tests should fail if lint errors occur * chore: update the lockfile (again), fixing a bug in airbnb config
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information: