Whenever I run npm start the same "error" message appears "No production canister_ids.json found. Continuing with local"
At first there seemed to be a proxy problem, detectable in the browser console. I managed to solve it by editing the proxy in webpack.config.js
However, the error on npm start continues.
I've already tried changing the versions of npm, webpack, webpack-dev-server, dotenv-webpack and editing the "start" in "package.json", but it doesn't work.
Can anyone recommend another solution?
Or how to identify exactly what the problem is?
enter image description here
Thanks :)
After all, it's just a warning that appears because I haven't deployed to the network yet :D
Thanks to Kyle Peacock for the help!
Edit: Updating webpack version to 4.10.0 in the package.json and running npm install fixed the issue.
Related issue from webpack repo: webpack/webpack#15951
Related
I am trying to install this script. I am trying to run npm install command. But this is not working. This is stuck after message idealTree:color-convert: timing idealTree:node_modules/c.
Could anyone help me to install this script ?
I tried it myself and had the same issue.
There might be an issue on the author's end or with some dependency.
Try contacting the author of the package to investigate the issue.
You can create an issue here: https://github.com/creativetimofficial/vue-notus/issues
nice you can delete your node modules and try again...
or you can try npm cache clean
if both fails you can try yarn...
Today i decided to start react native cli project. Everything works great since i want to add new lib of course using npm . So i ran npm install ... . And this command always stuck on
Image
idealTree: timing idealTree Completed in 3440ms
And nothing happened. So i tried to ran
npm install --verbose
And again stuck on the same place. Also clear cache npm cache clear --force and nothing happened again. I don'n know how to fix this
I have had npm install freeze on me numerous times, lately. I'm not sure of the cause. When that happens I follow these steps:
Kill the npm install process with ctrl+c.
Delete node_modules. If there are files that you cannot delete because they are currently in use, that may mean that the npm install process was not successfully stopped. Try opening Task Manager and ending all nodejs and terminal processes. If this fails, restart your pc and then delete node_modules
Clean cache and reinstall node_modules with npm cache clean --force && npm i
This has happened to me a few times before and all I had to do was kill my dev server before running npm install.
Hope that helps as well!
I had the same issue on node latest version v18.8.0 and npm v8.18.0, I just downgraded to node 16.6 using nvm and it worked fine.
For me, the issue was that I had node running for a separate project. Terminating the other node process fixed the issue.
When i opened my package.json i saw '~2.2.1' in front of react-native-gesture-handler which probably means that it was notinstalled properly
Just close all terminals and then open task manager and kill all the processes corresponding to NodeJS. Then install it again.
Hopefully it will resolve.
I also faced this problem and the solution was simple by stopping all the "nodejs terminals" that are working outside.
When you stop nodeJS Terminals running in the background, it will complete the current installation process.
enter image description here
When you want to add package on your project it is better to stop server before adding new package.
I had same problem but after doing this it is solved.
Installing an NPM package (in this case 'zos') hangs at :
>npm install zos
fetchMetadata: sill resolveWithNewModule http-https#1.0.0 checking installable status
Seems kind of strange as this has only recently started occurring. Other packages seem not to have this issue...
I am using the following environment:
Arch Linux
Node v11.9.0
NPM v6.9.0
I can install other npm packages without issues (eg, lodash, truffle, web3)
OK, I managed to fix the issue... last week I was having some issues with internet access in a new location with wifi so I had to hack around a bit with my /etc/resolv.conf file to get general internet access again... turns out that while that fixed my general browsing it had a knock on effect on npm installs!
So in summary to fix the issue I replaced my /etc/resolve.conf file which had only the following line in it:
# Generated by NetworkManager
nameserver 192.168.0.1
with a previous version of the file I had saved which had the following contents:
nameserver 127.0.0.53
options edns0
And Walah! Everything works again, including the 'npm install zos'....
Thanks to anyone who was looking into this for me!
Cheers
Rick
Getting one of the following intermittant errors when running npm run dev:
EPERM: operation not permitted, mkdir 'D:\projects\my_project\.nuxt\components'
EPERM: operation not permitted, lstat 'D:\projects\my_project\.nuxt
I tried npm cache clear to no avail. Some people attribute this issue to npm install folders shared on some network, not my case.
Note: this is a random issue. I just tried again after a couple hours and now it works. But when creating this question, it never worked no matter how many times I tried.
Any idea?
I had the same issue. I believe is related on VS Code.
I closed VS Code and stopped my console.
I rebuild Nuxt with 'npm run dev' and reopen VS Code.
Now is working.
To solve this issue is only
Stop dev, Close your CMD and Open CMD again and last you can npm run dev again
Hope this will help you :)
Same issue. I'm on windows with VS code. Closed terminal and run again with administrator, then it worked. Permission issue.
first close the vscode and the bash or cmd runner the project
then
just remove the ".nuxt" directory form root your project
I am using webstorm, and this problem also happened to me. I closed my terminal, then I closed webstrom and opened my IDE again and npm run dev. It solved my problem and maybe it can solves yours.
I was running Nuxt inside Docker, and it seemed that this issue was caused by my Docker images using up all the allotted space.
After cleaning up Docker images and containers, things started working again when I reinstalled.
Edit:
Never mind, this issue happens when I change branches with git. Fixing it is simply about restarting Docker.
For me the issue was that the file rights were given to root rather than to my user.
I fixed it using the command:
chown -R <user>:<group> .nuxt
Make sure to replace the <user> and <group>.
In my situation, dev script was already running so it prevented build script to access that directory.
I know this issue has been discussed in an old post. But in that scenario the developer was importing socket.io via a script tag. I am getting the same error on my local build and I have installed socket.io using npm.
Has anyone had a similar issue? How can this be corrected?
Turned out to be an npm cache issue for me. After several attempts I was able to resolve this by clearing my npm cache, deleting all of the modules, and then re-running npm install.