Migrate to one #763
Draft
Migrate to one #763
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
zoriya
force-pushed
the
feat/two
branch
2 times, most recently
from
7134fb4 to
f15ac3a
Compare
zoriya
force-pushed
the
feat/two
branch
5 times, most recently
from
9d228e9 to
281b3fa
Compare
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 a draft keeping track of the migration to one. This will allow us to delete the expo+nextjs setup and only use a single router + root package.json.
Blockers:
Can't access<head>nor add css during the ssr pipeline. Yoshiki can't be used as is.Babel config is not exposed so even if we migrate to unistyle, we wouldn't be able to set it up.