next export adds all hot-update files #5554
Labels
good first issue
Easy to fix issues, good for newcomers
Comments
|
Workaround is to adjust export script: // package.json
scripts: {
"export": "rm -rf .next out && next build && next export"
} |
timneutkens
added
help wanted
good first issue
|
PR |
|
Closing this in favor of #6009 |
8 tasks
kodiakhq bot
pushed a commit
that referenced
this issue
Jun 14, 2021
- Enables excludeDefaultMomentLocales by default - Adds distDir cleaning (See RFC #6009) - Adds support for `PORT` - Removes `router.events` from the server-side router as it should not be used server-side (long-standing todo that is potentially breaking). Note that it's still available as `Router.events` (import Router from 'next/router') and with `useRouter` in `useEffect`. Using it with `useEffect` is the correct way and I've updated the upgrading guide to reflect that - Added webpack 5 to the upgrading guide - Removed `Head.rewind` as it's been a no-op since Next.js 9.5 and can now be safely removed from user code Fixes #11408 Fixes #10338 Fixes #5554 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## Feature - [x] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. ## Documentation / Examples - [ ] Make sure the linting passes
flybayer
pushed a commit
to blitz-js/next.js
that referenced
this issue
Jun 16, 2021
- Enables excludeDefaultMomentLocales by default - Adds distDir cleaning (See RFC vercel#6009) - Adds support for `PORT` - Removes `router.events` from the server-side router as it should not be used server-side (long-standing todo that is potentially breaking). Note that it's still available as `Router.events` (import Router from 'next/router') and with `useRouter` in `useEffect`. Using it with `useEffect` is the correct way and I've updated the upgrading guide to reflect that - Added webpack 5 to the upgrading guide - Removed `Head.rewind` as it's been a no-op since Next.js 9.5 and can now be safely removed from user code Fixes vercel#11408 Fixes vercel#10338 Fixes vercel#5554 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## Feature - [x] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. ## Documentation / Examples - [ ] Make sure the linting passes
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
all in a title; details are below
Describe the bug
if you develop next.js site for awhile and then run
next exportin the out folder you will get a lot of hot-update files in anoutfolder, which are required only for development and redundant for prodThat makes
nowdeployment pretty slow, I unexpectedly got 248 files to deploy for my next-js based version of a blog.To Reproduce
full log
Expected behavior
outfolder should not have dev-only files, like hot-update filesScreenshots
System information
10.14 (18A391)7.0.2The text was updated successfully, but these errors were encountered: