* fix(ts): make ts-node register the right `tsconfig.json`
* setup guard & change require in nuxt-ts bin
* improve tests + test guard
* remove typescript-custom fixture
* Move TS unit test from `test/unit` to `packages/typescript/test`
* fix tests
* Bundle `@types/node` into `nuxt-ts` distribution
* feat(ts): Autogenerated tsconfig.json
* fix(examples): Update typescript examples
* fix(ts): Add `dist` & `tsconfig.json` to `pakage.json` files
* fix: add missing new line at the end of generated `tsconfig.json`
* add suffix if needed to `tsconfig.json` types during package build
* use `readJSON` over `readJSONSync`
* fix indentation in `nuxt-ts/tsconfig.json`
* use writeJson instead of writeFile
* split `nuxt-ts/src` in 2 functions + rootDir parametr + add tests
* add `fs-extra` to dependencies to prevent build warning
* JSON everywhere instead of JSON/Json
* fix: missing call to generateTsConfigIfMissing
* ask confirmation for tsconfig.json generation
* improvement: let compilerOptions.module as default
* improvements
* move from github link to friendly linkable local path
* add resolveJsonModule in default config
Co-Authored-By: kevinmarrec <kevin@marrec.io>
* Move `nuxt-ts` logic to `@nuxt/typescript`
* Upgrade to `ts-node@8.0.1`
* support named views for extendRoutes config
* fix lint errors
* fix lint errors 2
* some refactoring
* var rename
* fixture & unit tests
* fix: style
* nuxt-child named view example and test
* nuxt element with named view in layout
* lint
* feat: add store module HMR
* fix: replace export with window.$nuxt
Thanks to @pi0 for the suggestion :)
* refactor: apply only in dev mode on client side
* test: make store module test more descriptive
* fix: clear modules to apply HMR
* fix: remove console.log
* fix: e2e tests
* refactor: use void
- 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.
