Warning: Task "eslint:build" failed. Use --force to continue.

[abhisheknaiidu]

While running the " npm run grunt " command getting this Error.

[welcome]

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.

[lmccart]

hi @abhisheknaiidu sorry you're having trouble. have you tried running npm install? did that command execute successfully?

[abhisheknaiidu]

Yes, that worked fine infact! but if I'm running npm run grunt command, its giving error.

[lmccart]

I see, thanks. Can you please post the full readout that is excerpted above?

[abhisheknaiidu]

yeah sure. So, if I am running the "npm install" command im getting these two as warnings, I don't think it will cause any problem.

And after running "npm run grunt" command, im getting this error -

is this fine? or should i provide any more information ?

[jrlowent]

Hello All,

I am new to working in open source, and new to this project!

I am getting a very similar error when I run "npm run grunt". This error comes after following the instructions for the "Development Process" in the "Developer Docs", where I commit my first message to my local copy.

Thanks in advance for your help, and let me know how I can help you all.

Best,
Jake

[stalgiag]

Hi @abhisheknaiidu & @jrlowent thanks for your interest in contributing!

I tried to recreate this by setting up a new development environment and I wasn't able to recreate. I used the instructions from the Development Process section.

My system setup is:
os: Windows 10 build 18362
git: version 2.23.0.windows.1
node: v8.15.1
npm: v 6.41.1

Would you mind posting info about your development environment(s) as well? I have seen node or npm version cause problems in the past.

[limzykenneth]

@abhisheknaiidu It seems the npm version you are using is very old (v3.5.2), can you update that to the latest version and see if that works?

[abhisheknaiidu]

@limzykenneth After using node version 6.1.2 also I'm getting a error, but it's different from previous scenario's

[lmccart]

can you try updating to node v12 or v13?
https://hosting.review/tutorial/how-to-update-node/

[abhisheknaiidu]

@lmccart I have been using node v13 only, it is not working in that version also!

[jrlowent]

Hi @abhisheknaiidu & @jrlowent thanks for your interest in contributing!

I tried to recreate this by setting up a new development environment and I wasn't able to recreate. I used the instructions from the Development Process section.

My system setup is:
os: Windows 10 build 18362
git: version 2.23.0.windows.1
node: v8.15.1
npm: v 6.41.1

Would you mind posting info about your development environment(s) as well? I have seen node or npm version cause problems in the past.

=================================================================

Thank you for your help! Here is my development environment:

OS: Windows 10 version 1903 build 18362.449
Git: 2.23.0.windows.1
Node: 12.13.0
npm: 6.12.0

Here is my error message when running "npm run grunt" after arriving at eslint:build:

"Running "eslint:build" (eslint) task
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be
inferred.
⏎·······[Error/prettier/prettier]e\Github\p5.js\tasks\build\browserify.js:22:17: Replace·?·'p5-test.js'with

1 problem
Warning: Task "eslint:build" failed. Use --force to continue.

Aborted due to warnings.
npm ERR! code ELIFECYCLE
npm ERR! errno 3
npm ERR! p5@0.10.2 grunt: grunt
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the p5@0.10.2 grunt script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:"

[jrlowent]

@abhisheknaiidu & @lmccart,

Yesterday, I Installed the latest version of Python, added it to the Windows path, and ran npm update. I did not have the same issue after performing these steps. I am not sure if all the steps are necessary, but my branch coincidentally worked after this.

If you have any comments or suggestions, I would appreciate them. I hope this helps!

Best,
Jake