Error: ENOENT: no such file or directory, scandir - maven

I scaffold an app using jhipster which is microservice gateway using cassandra db and using maven to build which was building fine after scaffold.i ran gulp command to for the live reload of ui.
i made a change slighlty in navbar and home page of it.
which was also working file & made some changes in the json files of home & navbar & do some minor changes as adding the search box and other.
it failed to reload. I stop the gulp & maven & restarted them.
maven is building but again not loading the site in localhost
when i ran gulp it is showing me this error.
gulp
fs.js:952
return binding.readdir(pathModule._makeLong(path), options.encoding);
^
Error: ENOENT: no such file or directory, scandir '/home/hartron/foodnetteam/codebase/mandi/node_modules/node-sass/vendor'
at Error (native)
at Object.fs.readdirSync (fs.js:952:18)
at Object.getInstalledBinaries (/home/hartron/foodnetteam/codebase/mandi/node_modules/node-sass/lib/extensions.js:121:13)
at foundBinariesList (/home/hartron/foodnetteam/codebase/mandi/node_modules/node-sass/lib/errors.js:20:15)
at foundBinaries (/home/hartron/foodnetteam/codebase/mandi/node_modules/node-sass/lib/errors.js:15:5)
at Object.module.exports.missingBinary (/home/hartron/foodnetteam/codebase/mandi/node_modules/node-sass/lib/errors.js:45:5)
at module.exports (/home/hartron/foodnetteam/codebase/mandi/node_modules/node-sass/lib/binding.js:15:30)
at Object.<anonymous> (/home/hartron/foodnetteam/codebase/mandi/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
Could anyone tell me solution for this

I sometimes also get this error when starting my gulp server. My workaround is to just run:
npm rebuild node-sass
And then gulp starts nicely afterward.

Here's what worked for me
$npm update
$npm install
$node node_modules/node-sass/scripts/install.js
$npm rebuild node-sass

For my case it helps only after doing this command:
node node_modules/node-sass/scripts/install.js
And then there will be /node_modules/node-sass/vendor folder

Some files may not be available in the local version of NodeJS, and sometimes NodeJS does not send a message about it. In this case --force is helpful.
npm install node-sass --force
or
npm rebuild node-sass --force

rebuild node-sass or just reinstall everything in case node-sass rebuild of doesn't work.
npm rebuild node-sass
or
rm -rf node_modules && npm install
or
npm rebuild
or
npm ci
or
just delete node_modules manually and package-lock.json and run npm i

The vendor directory is created during npm install. Try deleting your
node_modules and running npm install.

It is a problem with older version of node-sass. It doesn't create vendor folder in node_modules/node-sass. I have updated the version of node-sass and it worked fine for me.
My older version of node-sass was 3.1.0
I simply did:
npm install node-sass#3.7.0
This should solve your problem as well.

I just fixed this error. It was because I was trying to run the project from the wrong folder.

Make sure you have the config.json file. Then do the npm install and npm start.
This might give this error if you don't have this config file.

No need to delete node modules, its because of your sass-loader version is different
Delete package-lock.json
npm uninstall node-sass --save
npm i node-sass --save

delete the node-sass folder from node\npm-cache
npm rebuild node-sass

I did the below code,
sudo npm rebuild node-sass
mvn clean install

Update your gulp-sass in package.json with new version
"gulp-sass": "3.1.0" // 3.1.0 or later
This is the link which i follow https://github.com/dlmanning/gulp-sass/issues/508

Related

Why npm run dev stuck on APP_URL?

Today when i tried to run npm run dev in Laravel 9 , it stucks at APP_URL line. Earlier there were no issues.enter image description here
Hope it's because of Vite
try with
npm run build
There is nothing wrong with your build. Laravel now uses Vite as front-end bundler. It is much more powerful than mix, so check out the documentation and get used to it. Or roll back to mix.
first solution : Laravel 9.19 replace the mixer with Vite, for Vite Configuration visit the official Doc of Laravel for Vite Bundling Assets (Vite)
second solution: install Laravel version 9.1.0 or lower
composer create-project Laravel/Laravel App_name 9.1.0
Uninstall and reinstall the npm package.
Delete the node_modules folder. and then run the following command
npm install
Later
npm install -g require

Laravel 9 [webpack-cli] TypeError: compiler.plugin is not a function

I downloaded a laravel 9 template and I am trying to run and use it but every time I try npm run dev I get the error [webpack-cli] TypeError: compiler.plugin is not a function.
I've solved the issue by reinstalling browser-sync-webpack-plugin which, according to the error, is the plugin that causes the error. Here are the following commands that solved my problem:
npm uninstall browser-sync-webpack-plugin
npm install browser-sync-webpack-plugin
It upgraded this plugin's package.JSON's line from "^2.0.1" to "^2.3.0".
I think I should update all my NPM plugins (see NPm commands npm outdated and npm update).
Usually it means that one of the plugins needs to be updated

Local gulp won't update

I have to use gulp with project, but the problem is that the local Gulp version is 3.8.11 and the global is 3.9.0. It doesn't matter how much I update it stays the same. I'm on windows 7.
Did this:
npm update gulp -g
cd myfolder
npm update gulp
I've also tried reinstalling a bunch of times but in the end it always comes up with:
CLI version 3.9.0
Local version 3.8.11
Any ideas how to start solving this?
npm update gulp -g will always update the global copy.
The warning is for your gulp in node_modules/gulp in your local project.
Navigate to your local project in terminal and do npm install gulp --save.

Phonegap installation error (npm)

I have been searching for a solution for two days now to setup Phonegap on my Windows 8.1
system without any success.
Whenever I try to install Phonegap through npm I get an error that I think has to do
with Cordova(-lib).
To install Phonegap I had to install Node.js (v0.10.28) on my system. After this I opened up Windows Powershell and issued the following command like instructed on the Phonegap website:
npm install -g phonegap
Output: (This is the only part of the error)
error notarget No compatible version found: cordova-lib#'lorinbeer/cordova-lib.git#configparser_module'
error notarget Valid install targets:
error notarget ["0.21.2","0.21.3"]
error notarget
error notarget This is most likely not a problem with npm itself.
error notarget In most cases you or one of your dependencies are requesting
error notarget a package version that doesn't exist.
I also tried installing just Cordova through the npm and then install Phonegap, but that
didn't solve anything either.
Running the Powershell with administrator rights also didn't help and tried solutions of other people who also had problems setting up Phonegap, but nothing works.
I really hope that someone could help me out here.
Thanks in advance.
Download the older version. I think there was a problem in the new one
npm install -g phonegap#3.4
I tried this and worked for me.
I had the same issue yesterday. If you check npm-debug.log, you'll notice that there is a permission issue ("Permission denied") when npm tries to access the cordova-lib git repository url. Actually, cordova-lib is a dependency for phonegap. So, it can't install it and I think that's why you get that error.
So, I tried this: install cordova-lib first then Phonegap. Yet, it still won't work; npm does not seem to check if cordova-lib is installed before trying to do it.
At this point, what I could do is to change the repository from which it retrieves cordova-lib. Here is the NPM install syntax:
npm install <tarball file>
npm install <tarball url>
npm install <folder>
npm install <pkg>
npm install <pkg>#<tag>
npm install <pkg>#<version>
npm install <pkg>#<version range>
This means I can install from a tar.gz file. Great! So, I just went to this page https://www.npmjs.org/package/phonegap to check the phonegap repository and performed these steps:
Download the zip of phonegap-cli repo (https://github.com/phonegap/phonegap-cli/archive/master.zip)
Unzip it
Open the package.json file and find the cordova-lib entry in dependencies (line 32)
Change the value to 0.21.3 which is the last version.
Recreate an archive of the folder to the tar.gz format
Open your CLI and run this command:
npm install -g path/to/archive/phonegap-cli-master.tar.gz
It should work now.
Hope that help!
I had a similar problem today too on Mac, even after Lorenzo said it should be all fine. Just running this:
sudo npm install -g phonegap
... produced loads of errors like this:
error: file ./objects/pack/pack-48c0ff4147fb7e8922546c4a857b98a1cb48e01f.pack is far too short to be a packfile
I combined Lorenzo and arpan shah's solutions:
sudo npm install -g phonegap#3.4
sudo npm cache clean
sudo npm update -g phone gap
... and it seemed to magically work.
Problem
We published with a dependency on a branch of cordova-lib. This fork appears unavailable when lots of requests are coming through (I think). One way or another, it's unreliable.
Changing the dependency to 0.21.3 will cause commands to fail, but will allow the install.
Solutions
update the 'cordova-lib' dependency to the npm published version '0.21.3'
**note, this will allow the install, but other phonegap commands will fail
wait for about 20 minutes, then npm update -g phonegap
testing an update to resolve this issue
further updates momentarily
update
We've pushed version 3.5.0-0.20.3 which should resolve this issue
$ npm update -g phonegap
if that doesn't work, try
$ npm cache clean
and reinstall phonegap
I tryed above comamnds npm cache clear and reinstall phoegap. It downloaded all libs but not command line scripts (phonegap command had still 3.4 as version). I found that better was to give command: npm install -g cordova (v 3.5)!

how can I install v.6.x of socket.io by NPM now?

I got lots of problem to work on v.7.x,but now I have to move my
project to a new server.so,I have to install socket.io again.
but,when I used "npm install socket.io" I got the last version.My
project using v.6.x,now I really cant install v.7.x,so,how can I
install v.6.x by NPM?
i think you can do it by
You can see listing by
npm ls socket.io
sudo npm install socket.io#0.6

Resources