Adds the ability to configure the props of keep-alive on nuxt-child.
## Types of changes
- [ ] 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
In development, I found it impossible to configure the props of keep-alive when using nuxt-child, like ```exclude```. This PR adds a special prop to nuxt-child named keepAliveProps to allow developer to configure it.
```html
<template>
<div>
<nuxt-child keep-alive :keep-alive-props="{ exclude: ['modal'] }">
</div>
</template>
```
## Checklist:
- [x] My change requires a change to the documentation.
- [x] I have updated the documentation accordingly. (PR: https://github.com/nuxt/docs/pull/836)
- [ ] I have added tests to cover my changes (if not applicable, please state why)
- [x] 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: abstract minify and use value for all modes
* change name to htmlMinify
* only override htmlMinify with legacy value in generate mode
* Use default options for htmlMinify and add override info to warning
* Remove redundant minification settings
* Override minification settings in generator
* Cleanup and add TODO for nuxt 3
* Improve warning
* set default minify option to "true"
* make tests pass again
* remove the culprit
* replace htmlMinify with html.minify
<!--- 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 (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Description
Webpack requires `uglifyjs-webpack-plugin@1.x`. thus `uglifyjs-webpack-plugin@2.x` may not resolve correctly. Also, the webpack team decided to go with `terser-webpack-plugin` (https://github.com/webpack/webpack/pull/8036).
## 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 passed.
Fix legacy gzip warning. Thanks to @liam-potter for pointing that out!
Related PR: #3863
## Types of changes
- [x] Bug fix (non-breaking change which fixes an issue)
## Checklist:
- [x] All new and existing tests passed.
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
Koya Ohashi
Vladlen
Alexander Lichter
Yamagishi Kazutoshi
Dmitry Molotkov
Clark Du
songyazhao
Jonas Galvez
ousiri
Felipe Lübe de Bragança
Pooya Parsa
Lajos Veres
Tatsuyuki Ishi
Sébastien Chopin
Pim
Ahad Birang
Indrek Ardel
Mihal Malostanidis