Closed jay-jlm closed 3 years ago
@jay-jlm I do not have ESlint set up locally or globally. And I do not recognize that engine.js
file, it is not part of the original project
Yes, engine.js
is just a file that I created, but any file will get the same error. (as long as you have your development environment configured to run Eslint locally).
Just to make it more clear: the point of the issue is that you can assume that most users these days would have a similar setup that would benefit from an existing local Eslint configuration, if one was available.
So this is more of a suggestion of a possible enhancement that would save users from having to configure Eslint manually for this project.
Hope that it's more clear now.
Getting the following error on VS Code
I suppose this project relies on a global Eslint installation? If so maybe I'd suggest migrating to a local configuration, since global dependencies are no longer the recommend way to use JS dependencies, unless in very specific cases.