Open Benjamin-Lee opened 3 years ago
I think you should include that property only if you were getting the below error:
โ Nuxt Warning
The command 'nuxt generate' finished but did not exit after 5s
This is most likely not caused by a bug in Nuxt.js
Make sure to cleanup all timers and listeners you or your plugins/modules start.
Nuxt.js will now force exit
DeprecationWarning: Starting with Nuxt version 3 this will be a fatal error
If you didn't get that in the first place, maybe you could try removing the property?
To clarify, I was getting that error (using Nuxt Firebase plugin) with static generation
I am making a new issue to track #493's problem, which I think was closed prematurely. Using the
terminateDatabasesAfterGenerate
option raises an error.Version
@nuxtjs/firebase: 7.6.1 firebase: 8.6.8 nuxt: 2.15.3
Reproduction Link
See #493
Steps to reproduce
Use
terminateDatabasesAfterGenerate: true
What is Expected?
The generation succeeds
What is actually happening?