Packages

@nuxt/types

2.18.1 · 28 Jun 2024MIT154.3k / 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/types From 0.7.2 to 0.7.9

7 releases in betweenevery note read

Other targets from 0.7.2Latest2.18.1
1
change to make
0
advisories fixed
9
new
2
fixes

Before you upgrade

Tick each one off as you go
  • Breaking0.7.4

Release by release

  1. 0.7.9

    12 Jun 20203 new · 1 fix
    • New

      Add env in the data context argument

    • New

      Add $nuxt.error({ statusCode, message }) method in the client side for calling the error page

    • New

      Add generated name in the routes generates by the pages directory (ex pages/index.vue will me the index name, pages/foo/bar.vue will be foo-bar)

    • Fixed

      Fix router.base when set to '/' or undefined, avoid generating 2 //

  2. 0.7.8

    7 Jun 20201 new
  3. 0.7.7

    26 May 20201 new
    • New

      We don't need to bind nuxt.render.bind(nuxt) anymore to use nuxt.render as a middleware (Issue #18)

  4. 0.7.6

    18 May 20201 fix
    • Fixed

      Make sure to generate the .nojekyll file empty

  5. 0.7.5

    25 Apr 20201 new
    • New

      nuxt generate now adds a .nojekyll file in the generated folder to tell Github Pages to not ignore the _nuxt directory (see github pages docs about it)

  6. 0.7.4

    Migration needed11 Apr 20201 new
    • Breaking

      pages/_error-debug.vue has been removed, now only pages/_error.vue should be defined

    • New

      Add Content-Length header in the server when rendering the html

  7. 0.7.3

    9 Apr 20202 new
    • New

      You can now access the application path with ˜, useful if you have others folders, see #16

    • New

      window.onNuxtReady(callback) is now a function, useful for attaching multiple functions to it, when is the app will be mounted, the callback will be called with the root application in the first argument

1 other line we could not sort, mostly version bumps

2 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.