Bump nuxt from 1.4.1 to 2.15.0 in /app

[dependabot-preview]

Bumps nuxt from 1.4.1 to 2.15.0.

Release notes

Sourced from nuxt's releases.

v2.15.0

💡 Highlights

⚠️This release introduces minor breaking changes. Update with caution ⚠️

• Minimum supported Node.js version is 12.0.0 (See nuxt/nuxt.js#8327 for why)
• Using jiti as new require engine with typescript support
• Plug and play works out of the box
• Allow opting-in to use postcss@8 (See nuxt/nuxt.js#8546)
• Several encoding issues resolved by consistently using ufo
• Components updated to v2 (please read migration guide)
• [Modules] When matching a webpack loader by name or query, should use includes instead of exact match (example)

🐛 Bug Fixes

• general
  • #8794 Ignore trailing slash in static payloads manifest
  • #8738 Encoding issues with payload paths
  • #8423 trailingSlash and child routes not working
• config
  • #8778 Prevent invalid css filenames in webpack output
• utils
  • #8780 serializeFunction fails with certain functions
• vue-app
  • #8759 Enable dynamic publicPath on server-side
  • #8701 Static payload fetching bugfixes
  • #8612 Check for Page.options before looking within
  • #8611 Don't remove req, res and query from context unless in full static mode
  • #8608 Ensure link.__prefetch exists before calling it
  • #8596 Add missing id attribute to noopApp
  • #8557 Scroll-to-top on route changes only
  • #8523 Set push on router instance rather than prototype
  • #8486 Do not preserve state when registering client-side dynamic module
  • #8802 Add leading slash for payload hydration
• server, vue-app
  • #8748 Address encoding issues with query params
• dev
  • #8697 Clearnup vue installed plugins from server in dev mode
  • #8556 Resolve module required by create-require in jiti
• cli
  • #8683 Disable parallel build behaviour when generating
• webpack
  • #8555 Can't resolve absolute url in css
• server
  • #8593 Fix HMR issue with serverMiddleware when router.base is set
• babel
  • #8545 Enable polyfilling of proposal core-js features
• vue-app, vue-renderer, utils
  • #8489 Respect trailingSlash setting for payloads
• generator

... (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 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 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 decision 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 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 dependency. The EOL also applies to the documentation.

Commits

• dcfb42b v2.15.0 [release]
• b96dd94 chore(deps): lock file maintenance (#8826)
• 3aa8ae3 chore(deps): update all non-major dependencies (#8825)
• dd0eea4 chore(deps): update all non-major dependencies (#8816)
• 7629cea chore(ci): use node14 for windows tests
• dc1c567 chore(ci): test against node@12 (minimum) and node@14 (lts)
• 53c40b9 chore(pkg): drop engines field
• e277bb2 fix(vue-app): align client fetch key with server (#8809)
• 9c24c11 fix(cli): re-enable serve-static redirect (#8814)
• 04646c5 chore: simplify contributors (#8808)
• 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 #272.