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.

Sign up for GitHub

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

Jump to bottom

ESlint does not behave correctly when importing fetch-charset-detection #247

Open
martinratinaud opened this issue Sep 15, 2022 · 0 comments
Open

ESlint does not behave correctly when importing fetch-charset-detection #247

martinratinaud opened this issue Sep 15, 2022 · 0 comments

Comments

@martinratinaud
Copy link

Hi all,

While using fetch-charset-detection on the Open Terms Archive, importing of this library is causing an eslint error with

error  Unable to resolve path to module 'fetch-charset-detection'  import/no-unresolved

I made a reproducable environment which behaves with the same error

Screen Shot 2022-09-15 at 10 33 07

This does not happen with other packages.

It might because there is no main in the package.json
martinratinaud added a commit to OpenTermsArchive/engine that referenced this issue Sep 15, 2022
@martinratinaud
disable eslint as it raises a false positive
3a8da5e 
and created the corresponding issue in their repo
node-fetch/fetch-charset-detection#247
@martinratinaud martinratinaud mentioned this issue Sep 15, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@martinratinaud