-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Reenable eslint on build command #325
Comments
Thanks so much for submitting an issue! We have received it, will review it soon and follow up. |
If this is still needed to be done then I can do it, just let me know. |
@secondl1ght, yes ut still needs to be done. Assigning it to you! 😎 |
Fix for issue ProjectProtege#325
Alrighty thanks, fixed with PR #339! |
As mentioned in PR #339, the aside from removing the configuration, the lint errors need to be fixed as well. |
Oops yes you are right I missed that part, for the unused variables do you want them commented out or deleted outright? |
If they are unused variables, remove them. No point on keeping dead code around. |
Ok and I think I should probably try building again and getting an updated output. Because I am sure things have changed to the codebase since this lint report was generated. |
Description
On build now with NEXT.js 11, eslint runs as part of the build. Currently it's erroring out with the following lint errors. Reenable linting on builds and fix the lint errors.
In next.config.js remove
Originally posted by @nickytonline in #324 (comment)
Related Issues
Depends on #324 being merged .
The text was updated successfully, but these errors were encountered: