Packages

@nuxt/config

2.18.1 · 28 Jun 2024MIT166k / weekRepositoryHomepagenpmAtom feed

Deprecated by its maintainers: Nuxt 2 has reached EOL and is no longer actively maintained. See https://nuxt.com/blog/nuxt2-eol for more details.What to use instead

Upgrading @nuxt/config From 2.5.1 to 2.18.1

55 releases in betweennotes for 17

  1. 2.5.1yours
  2. 35 releases
  3. 2.15.0breaking
  4. 8 releases
  5. 2.16.0breaking
  6. 3 releases
  7. 2.17.0security
  8. 3 releases
  9. 2.17.4security
  10. 2.18.0security
  11. 2.18.1target
10+
changes to make
0
advisories fixed
74+
new
75+
fixes

Counted from 17 of 55 release notes. Advisories are counted from the advisory database, in full.

Start here

Before you upgrade

Tick each one off as you go
  • Breaking2.16.0
  • Breaking2.16.0
  • Breaking2.16.0
  • Breaking2.16.0
  • Breaking2.16.0
  • Breaking2.15.0
  • Breaking2.15.0
  • Deprecated2.12.0
  • Deprecated2.7.0
  • Deprecated2.6.0

Security

  • Add non-applicable advisory GHSA-3h5v-q93c-6h6q

    2.18.0
  • 2.17.4
  • Mark GHSA-grv7-fg5c-xmjg as not applicable

    2.17.4
  • Exclude yaml exception vulnerability (build-time dep)

    2.17.0

Release by release

  1. 2.18.1

    28 Jun 20241 fix
    • Fixed

      webpack: Depend on earlier version of mkdirp

  2. 2.18.0

    Security fix27 Jun 20242 new · 1 fix
    • Security

      Add non-applicable advisory GHSA-3h5v-q93c-6h6q

    • New

      webpack: Migrate to memfs

    • New

      config: Add back md4 monkey-patch for wider ecosystem

    • Fixed

      vue-app: Don't throw if we can't read sessionStorage

  3. 2.17.4

    Security fix14 Jun 20245 fixes
    • Security
    • Security

      Mark GHSA-grv7-fg5c-xmjg as not applicable

    • Fixed

      types: Bump serve-static types to v1.15.7

    • Fixed

      generator: Use maintained html-minifier-terser

    • Fixed

      vue-app: Prevent double page mount

    • Fixed

      core: Don't skip loading runtime modules if one is improperly resolved

    • Fixed

      vue-app: Prevent error page mounting twice

  4. 2.17.3nothing new or fixed in the note

  5. 2.17.2

    24 Oct 20233 fixes
    • Fixed

      types: Prevent overwriting vue types in template

    • Fixed

      types: Don't pin webpack types to exact version

    • Fixed

      Remove md4 patch now that webpack has it in core

  6. 2.17.1

    14 Jul 20232 fixes
    • Fixed

      webpack: Downgrade dev-middleware to fix peer dep issue

    • Fixed

      webpack: Pin webpack-dev-middleware to 5.0.0

  7. 2.17.0

    Security fix9 Jun 20235 new · 3 fixes
    • Security

      Exclude yaml exception vulnerability (build-time dep)

    • New

      types: Support nuxt types for defineComponent

    • New

      csp: Support generating nonce for scripts and links in ssr

    • New

      webpack: Support passing function as postcssOptions

  8. 2.16.3

    17 Mar 20232 new · 3 fixes
    • New

      types: Add return type for error()

    • New

      webpack: Add node-fetch-native to externals list

    • Fixed

      types: Bring types from less into namespace

    • Fixed

      types: Sync vue type augmentations with Vue 2.7

    • Fixed

      config: Move preset to inner postcssOptions

9 other lines we could not sort, mostly version bumps
  • vue.config types should be optional

    2.15.0
  • Move @nuxt/types to nuxt mono-repo

    2.13.0
  • general: #6881, #6896 HMR support for server middleware

    2.12.0
  • core: Better module not found handling

    2.12.0
  • Using yarn as the package manager is more preferred as Nuxt is internally being tested against yarn

    2.6.0
  • Before upgrade ensure to remove yarn.lock, package-lock.json and node_modules

    2.6.0
  • After full install and testing, also consider upgrading other dependencies. The yarn outdated command can be used.

    2.6.0
  • Remove nuxt-ts dependency (2.4 users only)

    2.6.0
  • Create an empty tsconfig.json file. Nuxt will automatically generate it with defaults at first run, then you can edit it to fit your needs

    2.6.0

120 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.