Skip to content

v1.7.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Jun 18:59
· 127 commits to main since this release
v1.7.0
9245305
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Minor Changes

  • #50 182b907 Thanks @flyon! - create-app now picks between npm and yarn deliberately instead of silently preferring yarn:

    • If only one of npm / yarn is on PATH, that one is used.
    • If both are installed AND the user is running interactively, create-app asks Package manager [npm/yarn] (default: yarn):. Empty answer keeps the old default (yarn). Typing npm or yarn overrides.
    • If both are installed but flags (--app-name / --app-prefix / --app-domain) were passed, no prompt — yarn wins, matching the previous non-interactive default.
    • The chosen package manager flows through the install step AND the final "next command" hint, so the copy-paste line at the end is always cd my-app && npm start or cd my-app && yarn start matching what was actually installed (instead of always showing npm start with a yarn comment).

    Why this matters: scaffolding with yarn but then running npm start (without re-running npm install) used to leave critical packages unresolved at webpack-compile time. Picking one PM and reusing it removes that footgun.

Assets 2
Loading