reifyNode is a thing that hangs in my console a lot during npm i. I searched online to see what it is, and only found people mentioning in regards to issues. I just want to know npm is trying to tell me.
What does reifyNode mean? What is it doing? Example:
reify:fsevents: timing reifyNode:node_modules/lightningcss-darwin-arm64
Related
I have encountered a problem with npm which gives me this weird error.
It seems the error is not related to a specific file, but it is something that occurs for some reason. Unfortunately I can't share any code, but after a research I found it has something to do with cache (maybe?). The process is happening on a kubernetes pod with different environments for multiple npm/nodejs installations running in parallel.
Has anybody encountered this problem or has more details and information on the matter?
Will update the post accordingly, thank you.
Kindly see the above error that I am receiving while I am doing NPM Start for compiling Sass. Even though I tried to update the version such as this way (npm install -g nodemon npm WARN deprecated fsevents#2.1.3: Please update to v 2.2.x) but still getting error so please help with that and tell me the solution?
Hello My Gorgeous Friends Out There..!
In reference to above Question that earlier I asked and finally I became to answer it by myself only for those who are newbie and may be in case if they face the same issue so I would like to elaborate regarding the above issue which I faced and I resolved it.
I tried many npm commands which I am sure most of you all know it.
When I couldn't find any option even on many pages they said do this and this and so on..!
Only what I did I Search for (Live Sass Compiler) in vscode and Boom..! I am Happy with that.
Thanks to Me. :p
I keep getting this issue:
[snip of my issue][1]
I'm teaching myself node and am trying to make a CRUD RESTful application in my spare time. I'm working off this book:
https://leanpub.com/mean-machine.
For the past 3 days I've been stuck with this issue. It is specifically concerning the bcrypt-node.js . It's job is to hash passwords. Some things I have tried.
Downloaded python 3.5 as I got errors saying the runtime was needed to execute.
Setting python environment variable in PATH
npm uninstall and install.
Tried creating a new project, same issues cropped up.
npm clear cache
Since it is an old version of the bcrypt-node.js module changed the version in package.json from "0.0.3" to "0.0.5". I thought it could be a bug. Unlikely as that is.
I'm very new to node.js so I feel like I'm doing something silly that I just cannot see. Also I don't understand a lot of the information the command line is providing me. Thank you in advance.
EDIT 1:
Picture of my code.
Edit. (For future visitors) I needed to pay more attention to the various dependencies and a further understanding of JS in general to utitlise the power of Node.js, which is something I didn't do. Also recommended is a good understanding of Express.
A deeper understand of the npm is needed.
I found a fix through trial and error and some googling.
In case any one looks up this again in the future I entered:
npm install node-gyp -g && npm cache clean && rm -rf node_modules && npm installinto the command line and it appeared to fix the issue when I ran nodemon server.js
Fingers crossed it does not crop up again.
If someone would like to explain to me what exactly was the problem I had I would really appreciate it. I have a feeling a module or dependency wasn't installed correctly?
EDIT 1. Furthermore configure the PATH in your environment variables.
ie I created a path for python in the command line
PATH python = C:\Python27\python.exe & another PATH for MongoDB
i.e C:\Program Files\MongoDB\Server\3.2\bin
For some reason my npm stopped working with network suddenly.
I didn't really get why, so I decided to look through the stackoverflow questions but all the answers I could find were about running npm behind corporate proxies, but I work at home and I don't have a proxy.
Below is a couple of screenshots of my console with npm errors:
Maybe someone has already encountered that problem and knows how to solve it?
PS: I've read one guy saying that I just need to wait a bit and that npm servers might just be down, but it's already been for 2 days and I can't use npm:(
I hope someone might help)
Thanks to Bidhan, the command npm config delete proxy solved the issue.
I've looked through the different articles here, but I'm not finding out the answer I need, or don't understand necessarily what has been explained in other posts.
I downloaded node.js got my github up and have cloned the phonecat site, that part works fine. I can even check npm/node versions through cmd, but whenever I install using either "npm install" or "npm install -g" "Couldn't read depndencies" couldn't find package.json" has a long list of errors:
http://tinypic.com/1r54rjf4
I have tried caching, updating, restarting, uninstalling, reinstalling, giving permissions to fully allow windows system32 for commands. I have been reading for a few hours, and I am just at a complete loss here. Any help would be greatly appreciated!
When you don't specify a module to download, npm will look for a package.json. It's not finding one, which is why you're seeing all kinds of errors.
Is there a project you're working on? If you want to start a new one you can run npm init. If there's an existing one that has a package.json, you can navigate to that directory in your terminal and then npm install should work.
I didn't. I'm still wrestling with it. I'm not sure what to do about it either. I had one of my friends come over that's familiar with node and he couldn't figure it out. It must be a permissions issue somewhere on the computer. I can't figure out what else it could be.