Bump nuxt from 1.4.2 to 2.10.1

[dependabot-preview]

Bumps nuxt from 1.4.2 to 2.10.1.

Release notes

Sourced from nuxt's releases.

v2.10.1

🐞 Fixes

• vue-app, webpack
  • #6504 Remove consola from client
• utils
  • #6515 Fix error when router.trailingSlash is false
• generator
  • #6362 Remove trailing slash when no subFolders are used
• webpack
  • #6520 chunkhash and contenthash not work with extractCSS
• cli
  • #6525 Enable server for nuxt build when pages should be generated

🏡 Chore

• readme
  • #6511 Remove deprecated starter template

⚓ Dependency Upgrades

• vue-meta: Upgraded to v2.3 which fixes duplicated tags in SPA mode

💖 Thanks to

• Dennis Herzberg (@​dennis47528)
• Yuki Terashima (@​y-temp4)

v2.10.0

🌟Highlights

• Support for improved typescript runtime
• Experimental support for feature toggling for SUPER slim builds!
• Mitigate problems with nuxt server stocking during development
• Fix issues with internet-explorer in development mode
• Upgrade to terser webpack plugin v2
• Improved stability of loading-screen. No more endless loops (feat: prevent endless reloading nuxt/loading-screen#44) and show fatal errors (feat: show build error nuxt/loading-screen#45) for the initial build

🐛 Bug Fixes

• core
  • #6490 Clear resolver cache for project files dev mode
• vue-app
  • #6479 Error page layout not correctly applied in client-side rendering
  • #6473 Pass vm as arg to support data() with arrow function
  • #6433 Fix asyncData hydration when features.transition is false
  • #6430 Clear idle callback
  • #6217 Prevent looping on error during render of error page
• webpack
  • #6298 Fix consola IE compatibility

... (truncated)

Changelog

Sourced from nuxt's changelog.

Release Plan

Starting with version v2.4, Nuxt will adhere to a formalized release plan (as good as possible).
Also, an end of life for older major versions is defined with this document

Major versions (3.x -> 4.0)

Nuxt major releases are planned every 6 months. This depends on a few factors though:

• If there are no breaking changes waiting for a release, no new major version will be published. Instead, another minor one will be released.
• In case of unexpected major updates of important dependencies like Vue, Webpack, and so on, major versions might be released earlier than planned.

The goal is to provide a migration guide for each major version as well, as escape hatches, so existing code
won't "just break".

Minor versions (2.1 -> 2.2)

The release cycle for Nuxt.js minor versions is roughly 4 weeks.

Three of the four weeks will be used for actual feature implementations while the last week will be used for
testing, fixing bugs and thorough audits.

That also means a feature freeze for the next minor version after these three weeks.
Features that aren't ready will be moved to the next cycle. "Waiting" for features
(for a longer time) will be avoided as good as possible to keep releases lean, concise, predictable and digestible.

Patch releases (2.2.3 -> 2.2.4)

The last patch releases were mostly bundled fixes or single hotfixes.
In the future, fixes will be released as soon as possible after the actual PR/commit so people won't have to switch to nuxt-edge for bugfixes. This should improve the stability of Nuxt

Fixes can or will include:

• Updates of dependencies (for various reasons, like a "faulty/buggy" dependency or an newer versions that works better with the Nuxt.js code)
• Fixes for our code

Bugfixes for upcoming features won't be ported of course.

Edge Release Channel

After experimenting with nuxt-edge releases in the last time, the decisiion to do nightly releases for now instead of
releasing a version after each commit was made.

End of Life

Starting with v2.4, every major Nuxt.js version will have an End of Life.
Previous releases will receive security updates and bugfixes for one year and two weeks, counted from the first release on.
As Nuxt majors are approximately released once every 6 months, this will allow developers to "skip one major version" without being stuck with a broken or unsecure Nuxt.js dependency.
The EOL also applies to the documentation.

Commits

• 624c4c0 v2.10.1 [release]
• 9d9ae21 chore: update yarn.lock
• 9bfda1c chore(deps): update all non-major dependencies (#6545)
• 7883360 chore(renovate): lock memory-fs dep (#6541)
• 67d5601 test: refactor cli integration tests (#6537)
• a0ef4a3 Merge remote-tracking branch 'origin/2.x' into dev
• 6f2f13e chore(deps): upgrade execa to 2.1.0 (#6542)
• 010bb20 chore: upgrade babel packages to 7.6.3 (#6540)
• 91d7d02 chore(deps): upgrade vue-meta to v2.3.1 (#6539)
• 15fa12f [release]
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by pi0, a new releaser for nuxt since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #15.