-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New layout implementation #631
Conversation
🦋 Changeset detectedLatest commit: f69c212 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
How about size comparison? Imagine that our bundled |
Yeah this is my biggest concern of using styled-jsx too, another choice is to use a webpack loader to magically inject that global CSS import but then it will have this (existing today) issue:
|
It would be so good if Next.js supports page-level global CSS import... |
OK I managed to make it work 😄 |
Thank you for the review @B2o5T! |
I also have to deprecate the <Nextra.Tabs> use case, and built-in components won't be exposed by default. It now requires you to import This is because we are not always providing these components. So it causes issues since they might not be available (e.g. importing MDX directly). |
@shuding you are welcome! Amazing work |
* refactor loader and layout resolution * use global css import * test ssg * fix fast refresh * upadte snapshot * add changeset * remove @edge-runtime/vm * fix test * fix test * apply review suggestions * fix string template * update snapshot * deprecate the Nextra.* component * fix import * fix import * fix import
Closes #623.
The outcome of this PR: