I have an issue when I trying to start a new project.
I run 'nest new' to start a project.
And It took too long for installation.
And the result is below.
So I try to run 'npm install' manually.
I thought it is a 'ts-jest' download problem.
So I delete '"ts-jest": "29.0.3"' from 'package.json' devDependencies.
And it works well
I could simply format my PC and install again.
But this doesn't happen before and I'm curious about this.
Is there anybody know what cause it?
Ubuntu : Ubuntu 20.04.3 LTS
node version :16.19.0
nestjs version : 9.2.0
Related
I am trying to use parcel for the first time. I installed it to my project using the npm install parcel command. Then I tried to start the development server by running the command npx parcel src/index.html and nothing happens. I do not get an error. I allowed the connection when the firewall prompt came up. Does anyone know how to fix this issue?
Result when running npx parcel command
According to Devon Govett, the creator of parcel, this issue is related to an upgrade of napi-rs in the #parcel/source-map package, which was released sometime after Parcel 2.2.1. For now, they have reverted this upgrade and published #parcel/source-map v2.0.2.
Once I read about this update, I uninstalled parcel, deleted my .parcel-cache folder, and reinstalled parcel. Now the npx parcel src/index.html command works for me.
Sources:-
https://github.com/parcel-bundler/parcel/issues/7574#issuecomment-1023422239
https://github.com/parcel-bundler/parcel/issues/7598
Try changing the parcel in devDependencies to "latest". I did this when I had an issue using version 2.6.0 and it worked fine.
I'm trying to run the new Strapi version 4 application. But it returns this error.
Is there any bug in new strapi v4? or I'm doing wrong anything?
I'm using strapi official guide to start a new project
installation command npx create-strapi-app#latest molla-admin.
NodeJS v16
Windows 11
Error
ModuleNotFoundError: Module not found: Error: Can't resolve '#strapi/design-system/themes' in 'C:\Users\Admin\Desktop\molla-admin\.cache\admin\src'
at C:\Users\Admin\Desktop\molla-<anonymous>:10:1)
You might be thinking #strapi/design-system package is missing right? After that, I also tried to install both #strapi/design-system and #strapi/design-system/themes npm package
Still, it doesn't work. It returns a new error
ModuleNotFoundError: Module not found: Error: Can't resolve '#strapi/icons/CarretDown' in 'C:\Users\Admin\Documents\testing\strapi-v4-app\node_modules\#strapi\helper-plugin\build'
Should I go on for the next missing Module?
For me the issue was solved by installing #strapi/design-system (Node: v14.15.5, npm: 8.1.3)
npm install #strapi/design-system
Node version : 14.18.1
Npm version : 6.14.15
OS : Ubuntu 20.04.3 LTS
Steps I followed:
(I read somewhere that the latest version of node isnt working and
someone mentioned using the 14.18.1 version)
Downgraded NPM to use the 14.18.1 version and not the latest.
npm run build on the strapi project. This gave an error that its
missing #strapi/design-system.
npm install #strapi/design-system, you get another error that its missing #strapi/icons
npm install #strapi/icons . After this step there was an error relating to JSX scritps something to do with reactjs. So, in the next step , I updated Reactjs
npm install --save react#latest
npm run build again and this time SUCCESS!!
The strapi team should mention the issues on their homepage rather that making new users go through hoops to get it working. They need to make it clear that you can run into issues when using certain version of Node etc. As someone mentioned that they are aware of the issue yet no information in the homepage where new users visit to try it out. It should've been placed as a BANNER at the top in BOLD TEXT.
It's a known bug and they are working on a fix.
You have to use yarn in the mean time.
I can confirm that this bug is related to using Node v16. To get around the bug, I first ran:
nvm use 14.18.1
Afterwards, running the following resulted in successful compilation:
npm run build -- --clean
No need to attempt installation of #strapi/design-system.
I got this error because I was using Node v16. There was a message somewhere in my troubleshooting that you have to use A Node version >=10.X.X.X and <=14.X.X.X
I used NVM(Node Version Manager) to switch to 14.17.6 and it works
following solution worked for me:
yarn add #strapi/design-system
yarn add #strapi/icons
work on windows and ubuntu
node v14.15.0
yarn 1.22.17
npm 6.14.8
npm install #strapi/design-system
solution worked for me.
node 16.13.1
npm 8.1.4
macOS 12.0.1 on M1Max
After installing expo-CLI Version 3.5.0 to my computer so that I'm able to use it and then running npm start Node throws this error:" _xdl(...).ProjectUtils.readConfigJsonAsync is not a function. " I cannot find the solution to this online, it appears to be a new issue. Is anyone else running into this or have a solution for successfully running the program?
I also got the same issue. You don't need to downgrade node, just need to change some hashes on your project. (worked on node version 13.2.0 and expo-cli version 3.9.0 for me, although I have noticed that it also worked on LTS node 12.13.1 )
You can change the file located at:
\node_modules\metro-config\src\defaults\blacklist.js
From :
var sharedBlacklist = [
/node_modules[/\\]react[/\\]dist[/\\].*/,
/website\/node_modules\/.*/,
/heapCapture\/bundle\.js/,
/.*\/__tests__\/.*/
];
To:
var sharedBlacklist = [
/node_modules[\/\\]react[\/\\]dist[\/\\].*/,
/website\/node_modules\/.*/,
/heapCapture\/bundle\.js/,
/.*\/__tests__\/.*/
];
I need a solution as well. i have been using 3.5.0 version but today i tried to update it by mistake and i couldnt find a way yet to make it run normally. im starting to think the problem is server side or something updated is not compatible with old 3.5.0 version.
_xdl(...).ProjectUtils.readConfigJsonAsync is not a function
Screenshot of the error im getting
Edit: i just found the solution. new version of the xdl causes the error.
Fix:
Open up a command prompt(if you are on a windows machine), no matter which directory you are at, type commands below
npm uni -g --no-save #expo/xdl
npm i -g --no-save #expo/xdl#56.8.0
if you don't specify what version you want to install, npm or yarn will immediately select 56.8.1 version and installs automaticly and causes the error.
you need to downgrade to 56.8.0 version by typing the commands that i gave above.
I installed NodeJs LTS v8.11.3 for windows.
Then in cmd I wrote npm -g install create-react-app but I gave a an error that I need Node 4 or higher.
When I run node --v, I have got 0.12.2.
I didn't find how can I change it on windows. I already tried uninstall and restart computer, clean the cache, check windows path if nodeJs is here...
After that, still the same error:
*You are running Node 0.12.2.
Create React App requires Node 4 or higher.
Please update your version of Node.*
What should I do more? Thanks for ideas.
I have moved from 0.8 to 0.10, using the .msi package, overwriting the one installed on my system. Package problems were all fixed with npm update -g. Worked like a charm.
In case it does not work like a charm:
npm cache clean usually fixes the problem. Once the cache is empty, just run npm update -g again.
Ok, I solved it by these steps:
Clean cache from cmd.
Uninstall nodeJs from Program and Features.
Remove folder nodeJs from PATH variable.
Remove nondeleted folder nodeJs from ProgramFiles (here still were some files(?!)).
Restart Computer and after that install nodeJs from website.
After instalation - Restart Computer again.
Run cmd and checked by node -version.
Thanks for your time.
When going through the Cloud Functions docs and try to install npn. I get a bunch of errors when running this command from an Admin CMD window in Windows 10
npm install -g firebase-tool
This is the CMD output please advice on what this means. Why when I run as Admin it say "Please try running this command again as root/Administrator."
Here´s the complete log:
https://docs.google.com/document/d/19cO2iFSmYC7QkfcDg6BR5S4RgWkz-b6rq0aUmhLoEM0/edit?usp=sharing
I installed Nodejs 9.1.0 current version that was the problem. Now after uninstall and cleanup installing version 8.9.1 LTS recommended solved the problem
The docs should really mention the version compatibility