enter image description here
The error I get is in the picture
I deleted everything and reinstalled but it didn't work
In your package.json file add these 2 packages under dependencies :
"webdriverio": "^8.1.3",
"codeceptjs": "^3.3.7",
run npm run then npm install
Related
have been trying to install firebase through npm
using,
Npm install --save firebase
then it return an error saying
unexpected end of file while parsing input 3434DFDFSDFSGF.. and so on
and have tried diiferent solution on this platfoam such as
Npm cache clean --force
cache verify and so on...
please help...
Delete node_modules folder, go to package.json file add "firebase": "^7.7.0", in dependencies. You can which ever version is required.
Then run command npm install.
If this doesn't work check node js version. Check if your node js version is supported or not by firebase version which is intalled.
Because of fibers error on cPanel/CentOS/Cloudlinux servers, I'm using v2.0.0-beta.2 of #nuxtjs/vuetify in my Nuxt app.
But npm returns error on build or dev running.
No problem with v1.11.2, but the alpha and beta versions have error.
✖ Nuxt Fatal Error
Error: Module `#nuxtjs/vuetify` not found. Please ensure `#nuxtjs/vuetify` is in `devDependencies` and
installed. HINT: During build step, for npm/yarn, `NODE_ENV=production` or `--production` should NOT be
used.
package.json
"devDependencies": {
"#nuxtjs/vuetify": "^2.0.0-beta.2"
}
nuxt.config.js
buildModules: [
'#nuxtjs/vuetify'
]
I deleted the node_modules folder and re-runned the npm install and problem solved.
Go through the bellow commands
Delete node_modules
run npm i if you have previously npm installed on you machine otherwise run npm install then run npm i .
run npm run build
run npm run start
I tried Fred solution but didn't work out for me.
However I run this command npm install #nuxtjs/vuetify -D to install the vuetify component and the problem solved.
I have this error when I try to run my app in android
An unhandled exception occurred: [BABEL] C:\Users\UserName\Desktop\Ionic\MyProject\www\32-es2015.js: Could not find plugin "proposal-numeric-separator". Ensure there is an entry in ./available-plugins.js for it. (While processing: "C:\Users\UserName\Desktop\Ionic\MyProject\node_modules\#babel\preset-env\lib\index.js")
See "C:\Users\UserN~1\AppData\Local\Temp\ng-GJZvQx\angular-errors.log" for further details.
[ERROR] An error occurred while running subprocess ng.
as mentioned in this workaround
delete node_modules and package-lock.json
add "resolutions": { "#babel/preset-env": "^7.8.7" } to package.json
npm install npm-force-resolutions --save-dev
npm install
npx npm-force-resolutions
npm install again
run or build your app
if the error persist in future builds of your app try from step 5 before build it.
open package.json
"dependencies": {
"#babel/compat-data": "7.8.0"
}
run command
npm install
and then build your project and it should work.
I am trying to install rn-fetch-blob#0.10.15. but it's automatically installing the latest version i.e 0.10.16. I tried to install as follows,
npm install rn-fetch-blob#0.10.15
as per this solution, it should work as expected. But not working in my case.
Any help is appreciated.
Directly change your package.json file:
"dependencies": {
"rn-fetch-blob": "0.10.15",
...
}
And run: npm install --save
NOTE: With npm 5 and above you don't need the --save flag and package-lock.json file gets updated every time you do npm install
In my package.json file I have:
"dependencies": {
"#aws/dynamodb-data-mapper": "^0.7.3",
"#aws/dynamodb-data-mapper-annotations": "^0.7.3",
"#my-company/common": "file:../common",
...
}
#my-company/common specifies a local module which is installed by yarn.
However, when I run npm prune, this module is pruned.
I thought that including it in the package.json dependencies object would stop it from being pruned? Did I miss something?
For those who come across this, I discovered that running npm ls showed that there was an error with the common module.
Installing with NPM instead of Yarn fixed the issue.
Installing with Yarn did create the package within node_modules, however there was obviously an error somewhere which I couldn't uncover.