feat(gatsby-dev-cli): install deps if there are no gatsby deps but --forceInstall was used #27055
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…forceInstall was used
gatsbot
bot
added
the
status: triage needed
pieh
added
topic: dev tooling
and removed
status: triage needed
This was referenced Sep 25, 2020
Merged
Gatsby Cloud Build Reportgatsby 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 20m |
delete-merged-branch
bot
deleted the
chore/bundle-cli-and-recipes/gatsby-dev-cli
branch
This was referenced Jan 13, 2022
This was referenced Feb 10, 2022
This was referenced May 22, 2024
This was referenced May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just QoL:
Right now our test script for e2e and integration tests all use
gatsby-dev-clito install deps. Next PR in the series will removegatsby-clidep from https://github.com/gatsbyjs/gatsby/blob/master/integration-tests/gatsby-cli/package.json which would make our test setup just not install anything currently (evenjest).This is part of PR series:
feat(gatsby-dev-cli): install deps if there are no gatsby deps but --forceInstall was used(THIS PR)test(integration/gatsby-cli): use sandboxed directory to "globally" install gatsby-clichore(gatsby-recipes): bundle dependencieschore(gatsby-cli): bundle dependencies