Conversation
itsdillon
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes: blitz-js/legacy-framework#684
What are the changes and their implications?
This drastically cleans up the hacky code for switching between global and local execution of the CLI package.
When blitz cli is used inside a blitz project, it uses the locally installed version of blitz. The code for doing that was buggy. This fixes that.
Also, this makes the blitz cli use the development version if the cli is globally linked!! This makes it very easy to test dev versions of blitz with apps that aren't in the blitz monorepo.