Bump nuxt from 1.4.1 to 2.14.12 in /app

[dependabot-preview]

Bumps nuxt from 1.4.1 to 2.14.12.

Release notes

Sourced from nuxt's releases.

v2.14.12

🐛 Hot Fixes

• #8494 Fix issues with URL handling (resolves #8497, #8493, #8458, #8457)

How to upgrade?

Use yarn upgrade nuxt or npm up nuxt

v2.14.11

🐛 Hot Fixes

• #8462 Add url-polyfill to fix IE11 issue (URL is not a constructor) (resolves #8458)
• #8462 Update ufo to preserve relative links (resolves #8457, #8459)

v2.14.10

🐛 Hot Fixes

• Normalize routes and decode resolved query (#8430) (resolves #8429, #8442)
• @nuxt/components v1.2.2 (notes)

v2.14.9

🐛 Hot Fixes

• #8421 Only encode non dynamic path params

v2.14.8

🐛 Bug Fixes

• webpack
  • #8205 Allow transpiling packages in nested node_modules
• general
  • #8325 Handle route encodings and update vue-router
• vue-router
  • #8394 Force chidren to be required if default child is present (resolves #7823)
• cli
  • #8398 Respect router.trailingSlash when serving static files (resolves #8350)
  • #8337 Handle generate.cache.ignore as a function in ensureBuild
• generator
  • #8237 Nested route missing trailingSlash (resolves #8165)
  • #8344 Respect publicPath for static assets (resolves #7923, #7815)
• csp
  • #8352 Apply right csp header when status code is 304 (resolves #8353)
• vue-app
  • #8314 Handle missing payloads on full static (resolves #7717)
  • #8348 Warn if promises and functions are in fetch state (resolves #8338)
  • #8225 TriggerScroll when transitions is disabled
  • #8289 Use nuxt globalName correctly in nuxt-link and fetch mixin (resolves #8118)
  • #8280 Prevent redirection loop with URI-encoded path (resolves #8116)
• types

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

• bde4c5f v2.14.12
• a25bdd6 fix: fix issues with url handling (#8494)
• d85f4b9 v2.14.11 [release]
• 966796f fix: fix issues with route normalization (#8462)
• e97051a v2.14.10 [release]
• 1b38a12 test: update basic.dev (components module)
• 992f608 chore: update @nuxt/telemetry to 1.3.0
• 801ef0f fix: update @nuxt/components to 1.2.2
• fc51ca3 fix: normalize routes and decode resolved query (#8430)
• e9f380c v2.14.9 [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 #271.