De-experimentalize the public/ folder

[Timer]

Before we shipped Next.js 9 we removed a canary-only feature that was the public/ folder.

We should reintroduce the public/ folder as a replacement for the static/ folder, along these guidelines:

• Usage of the static/ folder should warn about deprecation and provide migration instructions (move static/ to public/, i.e. public/static/)
• Commands like next build and next export should forbid output into the public/ directory (i.e. distDir and out dir)
• Assets served from the public/ folder should have a default mime type applied (e.g. mime.getType(fileExt))

[haywirez]

This would pose a small problem for Gitlab pages - they require your out/dist dir to be /public. You could work around by renaming the folder with scripts, but still.

[Timer]

@haywirez the public directory is copied elsewhere on next export, meaning this would work fine.

[dzmitry-lahoda]

https://github.com/zeit/next.js/blob/master/errors/static-dir-deprecated.md

https://stackoverflow.com/questions/45505610/gitlab-pages-deployment-step-fails-after-successfull-build

"build": "next build && next export && cp -r out public",

Any proper solution without git bloat into public folder?

[balazsorban44]

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.