You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then as you create a local npm executable you can create a local yarn using this nippet
#!/bin/sh
cd $(dirname $0)
"node/yarn/dist/bin/yarn" "$@"
all ./npm install can now be replaced with ./yarn add.
Yarn generates a package.json when it installs first type angular-cli then the ng tool refuses to create the new app; so you should rename package.json before calling ./ng new client.
Thanks for the suggestion. I have no personal preference for npm over yarn, but it does seem to me to be more common. I'll leave this issue here in case anyone wants to copy your code.
Yarn is much better than npm.
You should include in the pom.xml
Then as you create a local
npm
executable you can create a localyarn
using this nippetall
./npm install
can now be replaced with./yarn add
.Yarn generates a
package.json
when it installs first type angular-cli then the ng tool refuses to create the new app; so you should rename package.json before calling./ng new client
.The test block in pom.xml should appear as:
BTW in your readme the block
is repeated twice.
The text was updated successfully, but these errors were encountered: