Skip to content
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

Resolve js/vue files after moving to eslint-plugin-n #383

Closed
wants to merge 1 commit into from

Conversation

juliushaertl
Copy link
Contributor

@juliushaertl juliushaertl commented Aug 11, 2022

Otherwise lint will fail if no extension is provided with node 16 and the latest release of eslint-config

Signed-off-by: Julius Härtl <jus@bitgrid.net>
index.js Show resolved Hide resolved
@skjnldsv
Copy link
Contributor

skjnldsv commented Aug 11, 2022

Are you sure? I did that too initially, but this is not the same
https://www.npmjs.com/package/eslint-import-resolver-node
https://github.com/import-js/eslint-plugin-import#resolvers

Currently Node and webpack resolution have been implemented, but the resolvers are just npm packages, so third party packages are supported (and encouraged!).

You can reference resolvers in several ways (in order of precedence):

as a conventional eslint-import-resolver name, like eslint-import-resolver-foo:

@skjnldsv skjnldsv added the bug Something isn't working label Aug 11, 2022
@juliushaertl
Copy link
Contributor Author

Right, at least it muted the lint errors for me, but might be probably better to keep it as per #292 and adjust the imports in the apps accordingly

@skjnldsv skjnldsv deleted the bugfix/noid/resolve-src branch August 11, 2022 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants