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.

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

getServerSideProps disables staticPrefix #16444

Closed
thgh opened this issue Aug 21, 2020 · 1 comment · Fixed by #16998
Closed

getServerSideProps disables staticPrefix #16444

thgh opened this issue Aug 21, 2020 · 1 comment · Fixed by #16998
Assignees
Milestone

Comments

@thgh
Copy link

thgh commented Aug 21, 2020

Bug report

Describe the bug

When using getServerSideProps, the staticPrefix seems to be disabled for that page.

To Reproduce

Enable staticPrefix in next.config.js

export async function getServerSideProps(context) {
  return {
    props: { translations: [] },
  }
}

Expected behavior

The page keeps working and applies the staticPrefix.

Actual behavior

The page requests the static resources without the prefix applied.

System information

  • OS: Azure
  • Browser (if applies): Chrome
  • Version of Next.js: 9.5.2
  • Version of Node.js: 12

Additional context

I have not debugged thoroughly, but removing getServerSideProps fixed the problem.

@Timer Timer modified the milestones: 9.x.x, iteration 8 Aug 21, 2020
@Timer Timer modified the milestones: iteration 8, iteration 9 Sep 8, 2020
@Timer Timer assigned Timer and unassigned lfades Sep 10, 2020
Timer added a commit to Timer/next.js that referenced this issue Sep 10, 2020
Timer added a commit that referenced this issue Sep 10, 2020
HitoriSensei pushed a commit to HitoriSensei/next.js that referenced this issue Sep 26, 2020
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants