I am trying to get rid of the following error message.
patch-package 6.2.2
Applying patches...
Error: Patch file found for package mongodb-query-parser which is not present at node_modules/mongodb-query-parser
This message appears when I try to install mongo-express. Locally this is no problem, because npm install keeps progressing after the error message.
But when I try to run it on gitlab-pipeline it exits the job.
Is there any workaround?
Temporary quick fix is to install mongo-express without the postinstall.
npm install mongo-express --ignore-scripts && npm install
That way the patch-package isn't called and at least the CI doesn't break. But I'm not sure how unsecure this is...
Hopefully going to be fix soon! I opened an issue
Cheers
Related
enter image description here
While creating a npm project I am getting this error.
But when I install yarn.
I don't know how to rerun the program.
Or is it because I installation problem.
Is using the latest version of node an issue.
Can Someone help me with this?
the strapi supports node version up to 18, you can check it here https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/cli.html#preparing-the-installation
there is flag for npm you can try to use:
npx create-strapi-app /appname --ignore-engines
However I doubt it would work, the workflow with yarn:
yarn create strapi-app /appname
If error still persists you can try to open your project with VS code or whatever IDE you use… Open terminal, do:
yarn --ignore-engines
yarn build --ignore-engines
yarn develop --ignore-engines
If that won’t help, it should give you another, more detailed error message that you should post then here…
I recently tried to launch my project on a new computer. I downloaded the source code from its repository and ran npm install to get all the needed packages.
However, when I run npm start or expo start:web, I get the error:
Cannot find module '#expo/metro-config'
I ran npm install #expo/metro-config and the install run without issue, but I still get the “Cannot find module '#expo/metro-config'” error.
The only post I saw regarding this error recommends editing the metro.config.js but I do not use one.
I am on SDK 42, and the project launches fine on my other computer. Any idea what is happening?
FYI, I use to perform this whole operation without any issue until now.
UPDATE:
I ran npm install -g #expo/metro-config and now I get the error Cannot find module 'resolve-from'
So it looks like maybe running npm install -g expo-cli doesn't actually install all the necessary packages? Could it be the issue?
I managed to make it "work" (get other missing packages errors down the line) by reverting to expo-cli 4.7.3. Anything from 4.8.0 and above will cause the error.
Something else is that on a fresh npm install, after running npm install -g expo-cli, if I try to create a project with expo init, I will get the error Error: Cannot find module 'kleur'. Running npm install kleur fix it, but maybe that's also a clue.
I’m getting that message after installing express globally.
I went through most of the solutions related to the /.bash_profile file and about exporting the correct PATH, but it still nothing works.
I tried this solution https://superuser.com/a/1081802 and it worked on the terminal, but when I close it and tried to execute the command express followed by the file I wanted to use, it ended up showing the same message.
Please help!
So I was looking for other kinds of solutions, and I remembered that I installed via the website and not by home-brew. Just in case, I uninstalled it and installed node again.
I run this:
npm install express -g
npm install express-generator -g
And up to this point it is now working.
My app was running perfectly but when I pull data from the git repository, I got this error.
I'm not understanding why I'm getting this error. Please help to get rid of this error and explain to me about this error.
The error is TypeError: undefined is not an object (evaluating '_core.pathUtils.urlToPathAndParams')
You may need to install #react-navigation/native.
I tried many time this method but got this error
I delete the node_modules and package-lock.json file and run npm install in terminal but error didn't remove.
The second method:
Then I did some similar steps
I run these commands:
rm -rf node_modules/
yarn install
yarn start --reset-cache
Now the error is gone.
try this one ( second method ) if you also getting these types of error.
This type of error occur because of
in your pull request you might be get some new npm in your
package.json file. so try to do npm install
or
try to remove node_modules and package-lock.json file
do npm install might be solve your problem
I encountered the same problem.
In my case, the reason is that I did not have #react-navigation/core at first, then I installed #react-navigation/core at the newest version, which is not compatible with my old #react-navigation/native.
After I updated my #react-navigation/native to have the same version with #react-navigation/core, the problem is solved.
You may want to check the versions of your #react-navigation components to see if they are compatible.
Check the installed packages
npm ls --depth=0
Install #react-navigation/native if you missing this package.
So I want to install react-native-keyboard-aware-scroll-view because <ScrollView></ScrollView> with <KeyboardAvoidingView></KeyboardAvoidingView> has some bug. But in my case, when I install it in command prompt and reloading my app it gives me error.
Source: https://github.com/APSL/react-native-keyboard-aware-scroll-view
This is the error in my app:
This is the error in my command prompt when installing it:
I have had this issue multiple times only in Windows I try these in the order usually.
npm install --force
Check if node_modules is set to read-only and remove if it is
Delete node_modules/
Check if any editor is opened that could have access to the root folder of the project
Reboot :(
Usually trying npm install after one of those steps will resolve it.
If these doesn't solve the issue, comment this solution and I will provide you with other solutions.
Because, this issue will also occur due to node installation error caused by your system antivirus.