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
Have you experienced this bug with the latest version of the template?
Yes
Steps to Reproduce
So this less a Bug more of a little annoyance, which could be helpful to include in the README for anyone who'd prefer yarn?
Specifically this is around setting up the package scripts to support yarn
Yarn install instead of NPM
Update npm run to yarn run in the scripts (To follow protocol, even though we'll ignore this down below)
Expected Behavior
yarn run dev starts the dev server as normal
Actual Behavior
You hit a few roadbloacks:
run-p dev:* fails with the error: No matches found: "dev:*"
Solution: Wrap dev:* in quotes -> run-p 'dev:*'
dev:server fails with the error: Invalid build flag: "--"
Solution: revert back to npm run build:server (Keen to know why this is 👀)
Technically it's only 1 roadblock with a simple solution if you keep npm run in your yarn project, but at the end of the day if you are using yarn there are reasons to keep yarn run around... I just dont have a simple solution for #2
Just thinking this could be an easy sentence in the README if you think it's worth having ^
The text was updated successfully, but these errors were encountered:
Have you experienced this bug with the latest version of the template?
Yes
Steps to Reproduce
So this less a Bug more of a little annoyance, which could be helpful to include in the README for anyone who'd prefer yarn?
Specifically this is around setting up the package scripts to support yarn
npm run
toyarn run
in the scripts (To follow protocol, even though we'll ignore this down below)Expected Behavior
yarn run dev
starts the dev server as normalActual Behavior
You hit a few roadbloacks:
run-p dev:*
fails with the error:No matches found: "dev:*"
Solution: Wrap dev:* in quotes ->
run-p 'dev:*'
dev:server
fails with the error:Invalid build flag: "--"
Solution: revert back to
npm run build:server
(Keen to know why this is 👀)Technically it's only 1 roadblock with a simple solution if you keep
npm run
in your yarn project, but at the end of the day if you are using yarn there are reasons to keepyarn run
around... I just dont have a simple solution for #2Just thinking this could be an easy sentence in the README if you think it's worth having ^
The text was updated successfully, but these errors were encountered: