I am trying to get the aurelia-materialize bridge plugin to work, and so far have been unable to do it with jspm, so I tried with webpack. I extracted the typescript-webpack skeleton into a folder, ran
npm install
then ran
npm install --save aurelia-materialize-bridge materialize-css
yet the install fails with error:
UNMET PEER DEPENDENCY webpack#2.1.0-beta.20
Any help getting this to work, or showing me any way to use materialize with aurelia would be much appreciated.
You should use npm install aurelia-materialize-bridge
append-g or --save if needed
Make sure after installation it is saved under jspm_packages/npm/
If you save it in a different directory make sure it is loaded correctly in your index.html
Related
I have some experience in react native but I am relatively new to the field. I have cloned a react native project but it is very old and it contains a lot of libraries that are also either depricated or conflicting. I want to make the project compile as its not compiling now too because of the conflicting library issues. Any help or guidance regarding what i should do to make it work?
I have tried a number of things like deleting node modules and package-lock and running npm install but it doesnt run so I used --force but it still didnt make it work then I used npm install --legacy-peer-deps and it still didnt work.
i tried to upgrade the specific libraries that were mentioned in the errors but they also failed.
right now I have no idea what should be done.
As of npm version 5.2.0+, we can update all our dependencies without installing any additional packages.
Run the command in the root of your project:
npx npm-check-updates -u && npm i
"npx npm-check-updates -u" the command just updates the package.json that’s why we need tonpm i after the update the package.json.
for more info click here
The issue I have is that npm start cannot start. I tried to fix with audit, deleted node_dependency directory and re-installed with npm, nothing works.
One concrete issue I see is:
The react-scripts package provided by Create React App requires a dependency:
"webpack": "4.44.2"
Yet, I also see npm -v webpack -> 6.14.14. How do I need to debug this?
Your npm -v webpack command is not correct. it will return npm version and not the webpack version.
Try npm ls webpack . you can also check your package.json file for the packages you have. or run npm ls for the full list.
make sure to install the required dependency as it states.
Eventually I could not solve the package problem with an informed debugging.
What I did was to (npm install --global yarn) and start the application through it (yarn start). It worked a lot to download the packages and eventually started the application.
So, I guess I need to switch to yarn after this point, which is ok, as long as it works :)
I'm trying to install vue-chart.js but unable to install. I tried by reinstalling npm and deleting package-lock.json file but doesnot work. I tried other methods as well but couldnot get succeed.
Please help me.
You must install the dependencies given in error. Listed below:
eslint#^5.0.0
For global install, use
npm install -g eslint
or For developement installation
npm install eslint --save-dev
Refer: https://www.npmjs.com/package/eslint
After deleting node modules and reinstalling npm solved my issue.
When I load vuetify via the vue-cli3, I get an error when i do npm run serve, saying there is a missing loader.
Docs etc and searches have come up blank.
This is a fresh project, no code loaded. Just following the instructions from the vuetify site.
Can anyone help?
I've got the same issues while creating new Vuetify app by official guide.
After adding vuetify: vue add vuetify
The missing step was installing new npm dependencies with: npm install
Later I run npm run serve and it started succesfully.
There is an issue in the documentation!
Try to manually install the package:
npm install vuetify-loader -D
you should check the vue-loader plugin path. in my case it is:
vue-loader/dist/plugin
Run npm cache clean --force. It should clear your npm cache.
For reference: https://github.com/npm/npm/issues/19072#issuecomment-345555468
I had the same problem. This whole thing worked out for me.
vue create your-app
cd your-app
npm i --save-dev --no-optional vuetify-loader vue-cli-plugin sass node-sass sass-loader
npm i
vue add vuetify
I know this looks redundant but it worked.
I got the same error when I cloned a repository and I installed the dependencies only on the master branch. When I switched to a different branch (git checkout different_branch) I forgot to install the dependencies there. So make sure you installed the dependencies before you launch the server.
Just had the same problem. In my case it was caused by placing the file vue.config.js in the top-level-folder (next to package.json) instead of in the 'src' folder.
Obviously there might be many reasons for this error, but maybe it helps someone...
do a npm install after adding vuetify as vue add vuetify then start server by
npm run serve
In your package.json: move #nuxtjs/vuetify from devDependencies to dependencies
just install the pacakge to devDependencies:
npm i --save-dev vue-loader-v16
After installing the dev dependency
npm run serve
I decided to remove webpack from one of my react projects as dependencies slow down performance and I wasn't really using it. I tried npm uninstall -g webpack, npm uninstall webpack, npm uninstall webpack webpack-cli, npm remove webpack, etc. I ran npm start after each of these commands to start working on my app again and every time I got the same exact answer: "Error: cannot find module 'webpack'". It seems to be based in the internal loader for the react-scripts but I don't know how to edit that. Thank you in advance for any help you can provide. Note: I did check my dependencies and webpack is not there in either the main or developer dependencies
Since you said something about react-scripts, i'll assume you are using CRA.
The whole build process is inside the react-scripts package, which means that you would need to NOT use react-scrips on you start and build scripts. If you get rid of react-scripts you might be able to get away with webpack.