-
-
Notifications
You must be signed in to change notification settings - Fork 760
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
Add support for "public" directory #523
Comments
PRs welcome. |
This worked for me:
|
@kachkaev Yes, that will work. I think what we should do is:
It'd be nice to support the changes to NextJs core while allowing a clear non-breaking "upgrade" path for users. |
You can also check for I found that this doesn't work on Now where, when built, the localePath for the server needs to be |
I was still deploying my Next.js app as serverless lambda's, should probably compile to a server target 😊 |
Is your feature request related to a problem? Please describe.
From
nextjs
9.0.6 and above thestatic
directory is moved topublic/static
. Is not mandatory to move it, but thestatic
directory will be deprecated in the future. More information here.Moving the
static
folder topublic/static
throws the next error:Describe the solution you'd like
The path
***/app/static/locales/es/common.json
should be***/app/public/static/locales/es/common.json
Describe alternatives you've considered
For an easy fix, we could keep as temp solution the locales at the static path.
Additional context
...
The text was updated successfully, but these errors were encountered: