Releases: nuxt-community/firebase-module
Releases · nuxt-community/firebase-module
v2.0.0
✨ New
- Added Firebase Performance that can now be accessed via
$firePerf
.
You now have to include your appId
in the Firebase config object:
config: {
development: {
...
appId: '<appId>'
},
production: {
...
appId: '<appId>'
}
}
Thanks to @ahmedHusseinF for the pull-request.
v1.4.1
v1.4.0
✨ New
- Added direct access to objects for all services, not only this.$fireAuthObj:
You can now access all the plain firebase objects like so:
Firebase Obj | Shortcut |
---|---|
firebase.auth | $fireAuthObj |
firebase.database | $fireDbObj |
firebase.firestore | $fireStoreObj |
firebase.storage | $fireStorageObj |
firebase.functions | $fireFuncObj |
firebase.messaging | $fireMessObj |
v1.3.2
v1.3.1
v1.3.0
v1.2.7
v1.2.1
v1.2.0
⚠️ Important ⚠️
In order to make a new feature possible (see below) we had to restructure nuxt-fire options in nuxt.config.js
just a little bit. Make sure to change yours accordingly:
OLD:
modules: [
[
'nuxt-fire',
{
config: {
apiKey: '<apiKey>',
authDomain: '<authDomain>',
databaseURL: '<databaseURL>',
projectId: '<projectId>',
storageBucket: '<storageBucket>',
messagingSenderId: '<messagingSenderId>'
},
devConfig: { ... }
}
]
]
NEW:
modules: [
[
'nuxt-fire',
{
config: {
production: {
apiKey: '<apiKey>',
authDomain: '<authDomain>',
databaseURL: '<databaseURL>',
projectId: '<projectId>',
storageBucket: '<storageBucket>',
messagingSenderId: '<messagingSenderId>'
},
development: { ... }
}
}
]
],
✨ New Features
- customEnv Mode:
Sick of relying on NODE_ENV? Want to define more than just two different Firebase configs? EntercustomEnv=true
! Just define a new environment variableFIRE_ENV
and name your configs after the value of that variable. You can find more information on how to implement in our docs.
☘️ Small Improvements
- Build error's are now displayed in red.
v1.1.0
✨ New Features
- Now nuxt-fire is REALLY just importing the Firebase products that you need, making your app lighter
- Nuxt-fire now also checks for missing or invalid devConfig while in
NODE_ENV===development
🐜 Bug Fixes
- During
NODE_ENV===development
nuxt-fire is no longer checking for a missing production config