Fix broken import paths #22
Open
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
I think `82c500c` when it was merged in `7710e1fcefec1d909ec91ef81c3a830fb5276f64` broke these paths. Incidentally, that merge was not rebased before it was merged :'(. I have another commit that updates the canary used, in the latest canary the css packages have been split out and there are some fun looking "BaseClass not a Constructor" type errors. So that is something to look forward to. For now, this commit gets the `npm run dev` command up and running again.
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.
1063ce3 Fix broken import paths
I think
82c500cwhen it was merged in7710e1fcefec1d909ec91ef81c3a830fb5276f64broke these paths.Incidentally, that merge was not rebased before it was merged :'(.
I have another commit that updates the canary used, in the latest canary
the css packages have been split out and there are some fun looking
"BaseClass not a Constructor" type errors.
So that is something to look forward to. For now, this commit gets the
npm run devcommand up and running again.