Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use the official Next.js base path functionality #70

Closed
kmjennison opened this issue Jun 26, 2020 · 0 comments · Fixed by #71
Closed

Use the official Next.js base path functionality #70

kmjennison opened this issue Jun 26, 2020 · 0 comments · Fixed by #71
Labels
code cleanliness Updating, cleaning up old code and workarounds, refactoring

Comments

@kmjennison
Copy link
Contributor

Should be officially supported soon:
vercel/next.js#4998 (comment)

We use workarounds. @area/workaround/next-js-base-path is the label in our code base for affected areas.
@kmjennison kmjennison added the code cleanliness Updating, cleaning up old code and workarounds, refactoring label Jun 26, 2020
@kmjennison kmjennison mentioned this issue Jul 16, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code cleanliness Updating, cleaning up old code and workarounds, refactoring
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update Next.js to 9.4.4 gladly-team/tab-web
1 participant
@kmjennison