-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix: avoid mutating nextConfig #598
Conversation
🦋 Changeset detectedLatest commit: 8c9b234 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
|
I'm unable to see the logs for Vercel – nextra-theme-docs-dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, but I would love to know the reason why it can't be defined under tsup.config.js as |
The Vercel – nextra-theme-docs-dev deployment is fixed now! |
Co-authored-by: Dimitri POSTOLOV <en3m@ya.ru>
* Fix: avoid mutating nextConfig * Fix: pass defaulti18n to nextra/loader * Refactor: make i18n mutation easier to read * Refactor: migrate index to TS and create a default i18n * Fix add index.ts tsup * Revert migration to TS * fix: wrong entry * Update packages/nextra/src/index.js Co-authored-by: Dimitri POSTOLOV <en3m@ya.ru> Co-authored-by: Shu Ding <g@shud.in> Co-authored-by: Yixuan Xu <yixuanxu94@outlook.com> Co-authored-by: Dimitri POSTOLOV <en3m@ya.ru>
While updating to beta.10, I got a TypeError on i18n.
This PR 'solves' the issue, but gives back a bunch of json-schema validation errors. I preferred to create a PR half-backed than open an issue.
Moved the file to TypeScript to avoid future problems. Not sure if it's desired, but I found myself doing something silly without TS, even in this PR.