Nuxt.js: Nuxt v2.10 - TypeError: Cannot read property 'keyName' of undefined`

Created on 2 Oct 2019  Â·  11Comments  Â·  Source: nuxt/nuxt.js

Version

v2.10.0

Reproduction link

https://github.com/nuxt/create-nuxt-app/issues/355#

Steps to reproduce

Repro steps present at link.

What is expected ?

Working server/default project.

What is actually happening?

This shows up in DevTools:
https://camo.githubusercontent.com/8f11ac3655907c26a60f8c161c006fe67f5f3424/68747470733a2f2f6d656469612e646973636f72646170702e6e65742f6174746163686d656e74732f3437333430363030343735313439393237352f3632383938363830373936363439383832372f756e6b6e6f776e2e706e67

Additional comments?

Issue identified using create-nuxt-app:
https://github.com/nuxt/create-nuxt-app/issues/355#

This bug report is available on Nuxt community (#c9854)
bug-confirmed bug-report pending

Most helpful comment

Got the same thing after upgrading to 2.10.0 on a project that works fine on 2.9.2.

Had to revert back in the meantime.

All 11 comments

Same issue here with 2.10.0 release.

Got the same thing after upgrading to 2.10.0 on a project that works fine on 2.9.2.

Had to revert back in the meantime.

Having a similar issue with a pristine SSR project in dev mode:
image

The errors says:
TypeError: "meta.getOptions(...) is undefined"

The screen flashes the content but then goes blank.

Doing a build and start in production works fine though.

With no chosen UI framework works well.

I'm having the same poblem but only on Ubuntu. On Windods 10 it works well by the way.

Can confirm I'm on Ubuntu

On Thu, Oct 3, 2019, 10:18 PM DennisKot notifications@github.com wrote:

I'm having the same poblem but only on Ubuntu. On Windods 10 it works well
by the way.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/6506?email_source=notifications&email_token=AAAFA5XOWIS7Y376HLXOIZDQM3G3DA5CNFSM4I42L6H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAKN7YA#issuecomment-538238944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAFA5TVWP2GXZYQ7CVSU7LQM3G3DANCNFSM4I42L6HQ
.

I'm having the same poblem but only on Ubuntu. On Windods 10 it works well by the way.

At first I used create-nuxt-app as following:

package manager: Yarn
UI framework: Vuetify
server framework: Express
Nuxt modules: Axios + PWA
Lint: ESLint + Prettier
test framework: Jest
rendering mode: SSR

I'm having the problem on a Windows 10 machine, can't confirm for Linux though. I had the project configured to use Vuetify and the above problem occurred. I checked if the same happens when no UI framework is being selected and indeed, it then works.

I then used this config:
package manager: Yarn
UI framework: none
server framework: Express
Nuxt modules: Axios + PWA
Lint: ESLint + Prettier
test framework: Jest
rendering mode: SSR

You can mitigate this issue by installing/upgrading to vue-meta v2.3.0 manually

Also see: https://github.com/vuetifyjs/vuetify/issues/9181

For me the issue is now resolved. I'm not sure if installing vue-meta is helping. When I do a pristine SSR project it works. An inspection in the yarn.lock learns me that vue-meta 2.3.0 is installed so I guess that indeed helped.

Problem disappeared in SPA mode for me in Nuxt 2.10.1, vue-meta is updated in this release

Thanks, the issue is solved in v2.10.1 indeed. Will close this issue because of that

Was this page helpful?
0 / 5 - 0 ratings

Related issues

o-alexandrov picture o-alexandrov  Â·  3Comments

surmon-china picture surmon-china  Â·  3Comments

bimohxh picture bimohxh  Â·  3Comments

uptownhr picture uptownhr  Â·  3Comments

danieloprado picture danieloprado  Â·  3Comments