-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node versioning issue #6865
Comments
when I got this error, I changed the version of the dependency in package.json file into the versions that available. the command is $ npm info [name of dependency you want to check] versions, and when you got the new version, go to package.json and change the version right |
for this case, it seems not have any relation with version. As I remember, when I got this error, I searched a file named getFilesFromRepo.js and do something with the code but I am not really sure which one. While you find the file, copy the code and the error to the chatgpt or else, they might help you, bcs I use them as well |
completel not working for me. |
I have the same problem. when I use node version 14 or 15, the reaction cli throws error. The error is different based on which version of node I am using(14 or 15) but it is related to a syntax error in a file related to reaction cli somewhere in the installed folder. Also when I use node version 20, reaction cli seems to work fine (reaction help does not throw errors) but I can not create a project. This is the error I get with node 15:
this is the error I get with node 14:
|
As per the docs reaction requires node v14 or v15, but after cloning the code for npm install node v18 is required and after that for running the code node v14 or v15 is required. and after i do npm install with node v18 i getting error.
npm ERR! code ETARGET npm ERR! notarget No matching version found for @reactioncommerce/[email protected]. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist.
The text was updated successfully, but these errors were encountered: