- Better insights and inspection for server bundle
- Remove all vue related dependencies from vue-renderer package as much as possible to reduce install size of nuxt-start
- Support for single file distributions (serverless)
- Remove server-bundle.json and use the standard .js files for dist/server
- Mitigate CALL_AND_RETRY_LAST Allocation failed errors. Most of the cases happen on JSON.parse() the part when loading bundle. (#4225, #3465, #1728, #1601, #1481)
- Reduce server dist size by removing escape characters caused by JSON serialize
- Faster dev reloads and production start by removing extra JSON.serialize/JSON.parse time
- Less memory usage
- General performance improvements and refactors
* Use consola on server error
* fix style
* ignore coverage
* use `consola.error(e)`
* formatting server error
* fix style
* offer a new port and listen
* fix style
* simplify return
* Revert "fix style"
This reverts commit 770347adb9.
* Revert "simplify return"
This reverts commit 26f2588b2f.
* simplified tests
* remove dependency `get-port`
* using port `0` to assign a random free port
* update `this.port` value with `address.port`
* For production, use `consola.fatal`
* pass options.dev from server to listener constructor
* add dev on constructor
* improve serverErrorHandler and close
* Update listener.js
* improve serverErrorHandler
* improve the way to handle listen errors
* fix missed line
* fully close old server before listening on a random port
* update listen.test
* feat: modern build
* refactor: use single module import for lodash
* refactor: add credit comment for modern plugin
* feat: ssr modern build
* fix: not null check for request
* fix: not null check for request.headers
* feat: add modern argument on build command
* refactor: simpilfy filenames for modern
* refactor: use packages/webpack src instead of dist in test
* test: add feature test for modern build
<!--- Provide a general summary of your changes in the title above -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (a non-breaking change which fixes an issue)
- [ ] New feature (a non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Description
<!--- Describe your changes in detail -->
<!--- Why is this change required? What problem does it solve? -->
<!--- If it resolves an open issue, please link to the issue here. For example "Resolves: #1337" -->
## Checklist:
<!--- Put an `x` in all the boxes that apply. -->
<!--- If your change requires a documentation PR, please link it appropriately -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly. (PR: #)
- [ ] I have added tests to cover my changes (if not applicable, please state why)
- [ ] All new and existing tests are passing.
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (a non-breaking change which fixes an issue)
- [x] New feature (a non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Description
Resolves#3920 by adding a warning during the build process and a small disclaimer into the default page component.
## Checklist:
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly. (PR: #)
- [x] I have added tests to cover my changes (if not applicable, please state why)
- [x] All new and existing tests are passing.
* feat: add tests to check for changed files
Make sure that if we are building or generating only files in buildDir and generate.dir are changed. If files in another location would also be changed due to a new config option, those locations should be guarded in lib/common/options so you cant set them lower then rootDir or srcDir.
* fix running tests inBand
use simpler path comparisons
* add debug logs for ci
use process.hrtime for waitFor test
* add debug logs for ci
use process.hrtime for waitFor test
* use writeFileSync should probably help
* use forEach instead of map when not returning a value
update waitFor test to compare values with jest
* fix appeveyor
* use lower limit than delay in waitFor test
revert isAppveyor export
The SPA fallback option should always be a string, if the user configuration was specifed as boolean true it should have been replaced by the default string value (currently 404.html) in lib/common/options.js
Added test on empty string
Added missing test for spa-fallback.html
* fix: appveyor test failure
* ci: bring back yarn cache
* ci: turn off matrix
* refactor: use babel instead of esm in jest
* refactor: use es modules in fixtures
