Webpack failed to compile npm start - node.js

I got a project that I need to work on. I forked the project from gitlab, unzipped it into my workspace folder, ran terminal and the following commands
node --version
npm --version
npm install
npm init
npm start
This should have installed all devDependencies (I turned production to false) and the server should be up and running. However, I'm getting the following error
`ERROR in .//src/client/index.js
Module build failed: Error: No ESLint configuration found.
at getLocalConfig ((dir)\node_modules\eslint\lib\config.js:162:35)
at Config.getConfig ((dir)\node_modules\eslint\lib\config.js:259:26)
at processText ((dir)\node_modules\eslint\lib\cli-engine.js:224:33)
at CLIEngine.executeOnText ((dir)\node_modules\eslint\lib\cli-engine.js:754:26)
at lint ((dir)\node_modules\eslint-loader\index.js:44:31)
at Object.module.exports ((dir)\node_modules\eslint-loader\index.js:181:3)
webpack: Failed to compile.`
I do have a eslintrc both on root dir and /src/client. What am I missing here ?

Related

bubblewrap init throws -bash: bubblewrap: command not found

I am building a PWA and following this tutorial to create a TWA. npm i -g #bubblewrap/cli runs fine. When I run
bubblewrap init --manifest=http://localhost:8000/static/manifest.webmanifest
or
bubblewrap init --manifest="http://localhost:8000/static/manifest.webmanifest"
or
bubblewrap init --manifest="<http://localhost:8000/static/manifest.webmanifest>"
I get this error:
-bash: bubblewrap: command not found
I have updated npm and bubblewrap based on this post and am still getting the error. My index.html is inside the static directory.
node v17.6.0
npm v8.5.1
java v17
jdk v11
Does anyone have advice on why bubblewrap isn't being recognized?

yarn dev failed in WSL (error: not an absolute path)

I install nvm and yarn in WSL, and my web project folder is on Windows F:/ , when I run yarn dev in WSL bash, vite come out an error:
➜ testProject yarn dev
yarn run v1.22.11
warning package.json: No license field
$ vite
> error: The working directory "/mnt/f/testProject" is not an absolute path
error when starting dev server:
Error: Build failed with 1 error:
error: The working directory "/mnt/f/testProject"
is not an absolute path
at failureErrorWithLog (/mnt/f/testProject/node_modules/esbuild/lib/main.js:1449:15)
at /mnt/f/testProject/node_modules/esbuild/lib/main.js:1131:28
at runOnEndCallbacks (/mnt/f/testProject/node_modules/esbuild/lib/main.js:921:63)
at buildResponseToResult (/mnt/f/testProject/node_modules/esbuild/lib/main.js:1129:7)
at /mnt/f/testProject/node_modules/esbuild/lib/main.js:1236:14
at /mnt/f/testProject/node_modules/esbuild/lib/main.js:609:9
at handleIncomingPacket (/mnt/f/testProject/node_modules/esbuild/lib/main.js:706:9)
at Socket.readFromStdout (/mnt/f/testProject/node_modules/esbuild/lib/main.js:576:7)
at Socket.emit (events.js:400:28)
at Socket.emit (domain.js:470:12)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
WSL Path:
➜ testProject where yarn
/home/gowsl/.nvm/versions/node/v14.17.5/bin/yarn
/mnt/c/Program Files/nodejs/yarn
➜ testProject where npm
/home/gowsl/.nvm/versions/node/v14.17.5/bin/npm
/mnt/c/Program Files/nodejs/npm
➜ testProject which npm
/home/gowsl/.nvm/versions/node/v14.17.5/bin/npm
➜ testProject which yarn
/home/gowsl/.nvm/versions/node/v14.17.5/bin/yarn
Maybe you are using yarn installed in Windows, that's so many packages that may not work with the WSL environment.
See Vite does not work on Windows WSL#4802. Maybe that can help you.
(Even if this issue has been solved, posted an answer here for a record.)

build dev failed: Cannot set property 'fileSystem' of null

I am on Linux Debian
I had this error a few times
I tried to install uninstall with npm install and npm uninstall
ionic -v
2.1.14
> ionic-app-scripts serve
[11:15:49] ionic-app-scripts 0.0.47
[11:15:49] watch started ...
[11:15:49] build dev started ...
[11:15:49] clean started ...
[11:15:49] clean finished in 3 ms
[11:15:49] copy started ...
[11:15:49] transpile started ...
[11:15:51] transpile finished in 2.19 s
[11:15:51] webpack started ...
[11:15:51] build dev failed: Cannot set property 'fileSystem' of null
[11:15:51] dev server running: http://localhost:8100/
My problem is different I installed ionic-app-scripts 0.0.47 like I read in the others answers but it doesn't work I have also tried
#ionic/app-scripts#latest but it doesn't work I have this error
build dev failed: Cannot set property 'fileSystem' of null
Install this : "#ionic/app-scripts": "1.0.0" version of app-scripts in your package.json.
This error came after npm update or ionic lib update (I wanted to test these commands... BIG MISTAKE).
Be careful with lib update.

Travis CI and Grunt Error: Grunt build failed and exited with 99 during '.'

I am trying to integrate Travis CI with a repository(forked on github). Everything is fine but Travis CI website is showing the following error under Job.
Fatal error: Unable to find local grunt.
The command "grunt build" failed and exited with 99 during .
I have added npm install in my .travis.yml and also defined script in my package.json file.
The grunt dependencies and gruntfile.js has also been properly set up.
Unable to find local grunt.
Is pretty explicit. Just add grunt to the dependencies of your package.json or run
npm i --save grunt
EDIT: OP's problem was actually due to a missing package.json at the root of the project.

Can't run yeoman application with grunt, cdnify.js

I've project to join so I cloned repo from git. I have installed npm install and then bower install, but when I try to run the app with grunt serve command, console returns this:
Loading "cdnify.js" tasks...ERROR
>> Error: Cannot find module 'chalk'
Running "serve" task
Running "clean:server" (clean) task
Running "wiredep:app" (wiredep) task
Warning: ENOENT, no such file or directory '/home/tomek/dev/mobilas/app/bower.json' Use --force to continue.
Aborted due to warnings.
The thing is, I shouldn't really change neither Gruntfile.js nor bower.json file.
Link I referenced in comment above fixed it for me... just had to run
npm install chalk
in the project directory as a work around until they get one of the grunt dependencies fixed.
Running below commands should fix your errors...
$cd /home/tomek/dev/mobilas
$rm -rf node_modules
$npm install
Now you should be able to run your app with $grunt serve command

Resources