I´m facing the same issue since I migrate my nx workspace to the latest version. The workspace contains an angular+nestjs aplications.
Everytime I try to install something that i need to install I´m facing with this. I try with --legacy-peer-deps flag and that is no good idea. enter image description here
package.json dependencies:
enter image description here
package.json dev-dependencies:
enter image description here
Solved I was having conflicts between package-lock.json
Related
When i install a new create-react-app and add babel-plugin-styled-components and add displayName option to babel-plugin-macros.config.js it isn't adding readable classNames as in the documentation -> https://styled-components.com/docs/tooling#babel-macro.
Here is a repo with the configurations https://github.com/Futekov3216/CRA.git
P.S i dont want to eject
Today I myself faced such a problem. The problem lies in styled-components itself. Macro in styled does not work since version 5.2.2, and it is not known when it will be fixed. Simplest solution:
npm i styled-components#5.2.1
This problem still persists in styled-components v5.3.3. Visit this to know more about the issue. At this moment you can install styled-components#5.2.1 as mentioned by #mxpv for getting the Component's name along with generated classes.
The issue causing this problem has been resolved.
Ensure that the version of babel-plugin-styled-components has at least version 2.0.3 by installing the package (as a dev dependency). The macro should work with the latest version of Styled-Components.
npm install -D babel-plugin-styled-components
--or--
yarn add -D babel-plugin-styled-components
nodejs version 14.17.5
vue native version 0.3.0
I am developing an application that requires navigation in APP.
When i give command "npm run start" the application successfully runs.
Package.json dependencies installed:
enter image description here
For navigation when i run command "npm install view-native-router" it shows the error message as below:
enter image description here
Does anybody have the idea what could possibly have gone wrong? Is it a compatibility issue ?
It seems this is not the first time we have a peer dependency problem here and the last issue was marked as solved.
https://github.com/GeekyAnts/vue-native-router/issues/45
Since you have a higher version of vue-native-core in local, try add --legacy-peer-deps to npm install to see if works.
Though --force or --legacy-peer-deps may work for some but not everyone.
My solution is to start using yarn! Install it by the following:
$ npm i -g yarn
After its installed, its advised that you delete the project and redo the vue-native-cli init command so it can use yarn from there, but you can also just directly use the following command without deleting the project:
$ yarn install vue-native-scripts
I have a problem with the nuxt project deploy on cpanel
Please, if anyone can fully guide me, thank you for running on the host
The image of the errors is available in the following links
enter image description here
enter image description here
To solve this problem, I installed the nuxt-start package before npm run build,
npm i --save nuxt-start
then
npm run build
and then
npm run start,
and the problem was solved, I said maybe this solution was needed for other people
guys,
I found the answer
node-js-is-not-installed
and I have the same problem
actually, I have nodejs
sudo apt-get install nodejs
Reading state information... Done
nodejs is already the newest version (8.10.0~dfsg-2ubuntu0.4)
.
but if I try to build I coach Gradle exception like
Node.js is not installed. Visit https://nodejs.org/en/download/ to install it.
Open File
unfortunately, steps by issues/3745 don't resolve it fo me
enter image description here
any help would be appreciated.
I had a identical problem earlier today. But I'm on a Mac. Same behaviour as you experienced.
I've try to reinstall node, and several rebuilding of my project but none of those worked.
In the end, I started over. Seems that the installation of the amplify cli did not went throught the previous time.
npm install -g #aws-amplify/cli
But I've come to another problem with the manifest.xml right after that. I think both are related...
And adding this to my manifest did the job : 'tools:replace="android:name"' (for reference if this problem follow : https://github.com/aws-amplify/amplify-android/issues/532 )
Run this in your project directory and then resync:
npx amplify-app --platform android
At least, this helped me
Did you install amplify using sudo? That has solved my problem.
Also using Mac OSX
Looks like you may not have proper write permissions on node_modules folder, use chmod 777 your_node_module_folder
I have created a project using Jhipster v4.0.5. Now have upgraded generator-jhipster to latest one i.e. v4.0.7 and tried to upgrade my existing project manually. But upgrade is not happening because no single file is changed after using command yo jhipster or yo jhipster --with-entities.
Have confirmed this through '.yo-rc.json', it is still showing {"jhipsterVersion": "4.0.5"}.
Does anyone know fix for this issue ?
You're probably using the generator-jhipster in your project's node_modules folder, delete it and re-run npm install or yarn install.
Why don't you use yo jhipster:upgrade rather than re-generating everything and losing all your customizations? See documentation