-
Notifications
You must be signed in to change notification settings - Fork 3.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
Help Request: Why are my lint tests failing? #8694
Comments
@nashmia-riaz It is probably a bug in |
@nashmia-riaz can you report using a proper help request template? Right now there are quite a lot of missing information if we are to troubleshoot. Also, while may not be written on that template, but do write down your Node.js version as well. |
@sukanta-27 I am up to date with the master. Upon further tinkering, I have found out that the tests do pass in cmd, just not in powershell or git shell (which i was using earlier). So, I assume that the problem is local. @wkurniawan07 apologies about not using the template earlier as I think the problem is with configurations on my machine. |
@nashmia-riaz I may have an idea of what's happening, but does this still happen? |
@wkurniawan07 I recently reset my laptop in hopes that it was a configuration issue on my machine, but it didn't go away. |
When I run 'npm run lint:js', it results in an error for every single .js file in dev/js. The resulting error is something like this:
error Casing of ../main/instructorCourseEnrollPage does not match the underlying filesystem import/no-unresolved
In addition to this, the webpack-main.config.js has the same error as well. The ./gradlew lint test, however, does pass. The error occurs on my local unmodified master branch. I have tried running npm install and npm run build, tried running the server again but in any case, I keep getting a massive list of errors on npm lint:js only.
What is the possible reason for this? And how can it be resolved?
The text was updated successfully, but these errors were encountered: