Releases: nuxt-community/firebase-module
v5.0.3
v5.0.2
v5.0.1
v5.0.0
Version 5 brings various optimizations in the Auth module.
We moved the Auth initialization functionality out of experimental an introduced a new experimental functionality, SSR Auth Server Login.
‼️ Breaking Changes - Upgrade from v4 to v5 ‼️
Follow the upgrade guide here
Changelog
See changelog here.
v4.0.0
With v4, nuxt-fire became an official nuxt-community module. <:o)
With this, the GitHub repository as well as the NPM location package name have changed.
In addition to that, nuxt-fire was renamed to @nuxtjs/firebase, to make it clear that this is the official Firebase module for Nuxt.js.
To make it consistent, we also changed certain namings within the module, so when upgrading from v3 to v4, you will have to change the following in your code:
‼️ Breaking Changes - Upgrade from v3 to v4 ‼️
1 - Rename module import in nuxt.config.js
// Old
modules: ['nuxt-fire'],
// New
modules: ['@nuxtjs/firebase'],
2 - Rename module options key in nuxt.config.js
Only if options are not set directly in the modules-array:
// Old
fire: {
// all the options
}
// New
firebase: {
// all the options
}
3 - Rename types in tsconfig.json
Only if using typescript:
// Old
{
"compilerOptions": {
"types": ["nuxt-fire"]
}
}
// New
{
"compilerOptions": {
"types": ["@nuxtjs/firebase"]
}
}
4 - Rename Helpers import path
Only if using helpers:
// Old
import { **helperFunctionName** } from 'nuxt-fire/src/helpers'
// New
import { **helperFunctionName** } from '@nuxtjs/firebase/src/helpers'
After all these changes, don't forget to rerun npm install
or yarn
and restart your IDE (e.g. VSCODE), then all should be good.
v3.5.5
🐜 Bug Fixes
- #86: Fixed an issue with Firebase Messaging Service-Worker initialisation.
☘️ Small Improvements
- onFirebaseHosting:
onFirebaseHosting
is now a global option which, once yet, is active for both the Firebase Authentication as well as the Messaging service workers.
‼️ Important: If you hadonFirebaseHosting
defined onmessaging.onFirebaseHosting
, make sure to delete it there and define it directly on the nuxt-fire option objectfire.onFirebaseHosting
(see here).
Thanks for @zhuharev and @wandriputra for reporting the Messaging sw issue.
v3.5.4
v3.5.3
v3.5.2
🐜 Bug Fixes
- Firestore:
enablePersistence = true
used to throw an "unsupported" error on server-side. It now does not get triggered on server-side anymore.
☘️ Small Improvements
- Firestore:
enablePersistence
can now also take an object which gets passed down as the official enablePersistance options, allowing e.g. to setsynchronizeTabs: true
Many thanks to @mentAl-maZe for the pull-request!
v3.5.1
✨ New
- Added SSR option to Firebase Auth:
This option automatically creates a service worker and a serverMiddleware that handle token refresh on client side and token validation on server side. The validatedauthUser
object can then be accessed innuxtServerInit
.
// In the nuxt.config.js nuxt-fire settings:
auth: {
initialize: {
ssr: true
}
},
For more information check out the Firebase Auth in SSR/Universal Mode Tutorial.
- Added SSR option to Firebase Auth:
⚙️ Maintenance
- Docs: Split up Helpers & Advanced in two categories
🐜 Bug Fixes
- Fixed bug in error handling of
fireStore.enablePersistence()