Nuxt.js: `nuxt build` fails at generating pages in spa mode

[alexkcollier]

Version

v2.10.0

Reproduction link

https://gitlab.com/alexkcollier/nuxt-build-repro

Steps to reproduce

1. Create nuxt project
2. Set mode to spa in nuxt.config.js
3. yarn build

What is expected ?

Build succeeds

What is actually happening?

FATAL Cannot read property 'renderRoute' of undefined

Additional comments?

yarn generate works as expected, and so does building in universal mode.

_{This bug report is available on Nuxt community (#c9850)}

[1001v]

I have the same issue on 2.10. There're no problems with 2.9.1.

[AndrewBogdanovTSS]

It happens not only in SPA mode but also in Universal, with and without a --modern flag. Dev mode is working fine though

[Teranode]

Can also confirm this happening with 2.10.0
2.9 and below works fine.

[AlexSwtlsk]

Same here

[sbrieuc]

Same here

[AndrewBogdanovTSS]

Guys, please, do not pollute the topic with the same messages. It's already clear that a lot of us have this issue

[moritzsternemann]

Looks like the breaking change happened in the @nuxt/[email protected] update. Works fine using 2.9.1.

[liyasthomas]

Build fails in Docker/Local/CI. Same here while generating pages in 'spa' mode.

TypeError: Cannot read property 'renderRoute' of undefined

[josepjaume]

Same happens to me on 2.10.0 but I tried reverting to 2.9.1 without success - maybe it's cause a transient dependency?

[AndrewBogdanovTSS]

@pi0 @manniL maybe you could provide some update on whether this issue is being addressed by the Nuxt team? Thank you

[jmartinezuk]

Same here. Went back to 2.9.1 until it's fixed.

[SamJakob]

I had this issue but I went back to 2.9.2 which also worked fine.

[catisnorm]

Same happens to me on 2.10.0 but I tried reverting to 2.9.1 without success - maybe it's cause a transient dependency?

Did you removed node_modules and package-lock?
https://nuxtjs.org/guide/upgrading#npm

[madmod]

I ran into this after removing package-lock.json and node_modules while working on something unrelated. A fresh npm i with package.json set to "2.9.2" fixed the issue.

[vinayakkulkarni]

Related issues: #6514 & #6513

[riux]

I imagine that this error is solved in the next version

[AndrewBogdanovTSS]

@riux it better be since now 2.10.0 is not usable for many people

[edellaq]

I'm not very fond of these things, but while tweaking here and there think I was able to build my SPA using 'npm run generate' instead of 'npm run build' (that gave the error)...

[vinayakkulkarni]

Fixed via https://github.com/nuxt/nuxt.js/commit/136777de1d7924f052c803c6397530de80bdea50

[riux]

I still have the error after changing to nuxt 2.9.2 (remove node_modules and yarn.lock from src / and from function /). This only happens when deploying in firebase hosting. The error occurs when I update the "f5" page in a different index path (domain.com/video/id_video). I clarify that this error does not occur in (yarn dev, nor in yarn start)
firefox

chrome

[laitingyou]

Waiting for a new version to be released.

[vinayakkulkarni]

this has been already fixed in #6525

6529 is v2.10.1

[riux]

I update to that version it only shows me v2.10

[AndrewBogdanovTSS]

@riux because Nuxt 2.10.1 wasn't officially released yet. You should wait. And please, use English

[alexkcollier]

[email protected] has been released, fixing the issue

[riux]

Well, I haven't updated to the new version yet. But I discovered that this error occurred for two reasons: 1) .Use the nuxt functions (asyncData, fetch) on a page with dynamic URL (search / _stringSearch.vue), then I had to change these functions tocreated () {. ..}.
2) I also found myself in the need to enclose
content of my page (search / _stringSearch.vue), with <client-only> .... </client-only>. My development environment is a universal application that uses the firebase and firebase hosting functions. As I mentioned, the error occurred at the time of the test in Firebase Hosting (Nuxt Build, Firebase Implement)

[alexkcollier]

You may have better luck creating a new issue. What you're reporting
doesn't seem related.

On Fri., Oct. 11, 2019, 6:25 p.m. Riux, [e-mail] wrote:

Well, I haven't updated to the new version yet. But I discovered that this
error occurred for two reasons: 1) .Use the nuxt functions (asyncData,
fetch) on a page with dynamic URL (search / _stringSearch.vue), then I had
to change these functions to created () {. ..}.
2) I also found it necessary to attach the content of my page (search /
_stringSearch.vue), with
Page content . My development environment is a universal application that
uses the firebase and firebase hosting functions. As I mentioned, the error
occurred at the time of the test in Firebase Hosting (Nuxt Build, Firebase
Implement)
[image: image]
https://user-images.githubusercontent.com/9002215/66688326-c72f9f00-ec4b-11e9-9dc9-d21e7b16b976.png
[image: image]
https://user-images.githubusercontent.com/9002215/66688359-e0d0e680-ec4b-11e9-8e3f-8366739e253f.png
[image: image]
https://user-images.githubusercontent.com/9002215/66688389-078f1d00-ec4c-11e9-966c-b78040180cc9.png

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/6500?email_source=notifications&email_token=AFOMXYD23Z3LCQUWXSTAD5TQOD4NVA5CNFSM4I4XHWD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBLUZQ#issuecomment-541244006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFOMXYEFKK3MT72GGJLAFPTQOD4NVANCNFSM4I4XHWDQ
.