* 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