Skip to content

Releases: nuxt-community/firebase-module

v3.4.0

09 Dec 03:37
7db1c19
Compare
Choose a tag to compare

✨ New

* Firebase Auth in Universal Mode: Added functionality that automatically creates a cookie that gets sent to the server in the initial request that can be used for server-side authentication
* getAuthUserFromCookie() Helper: Added helper that supports parsing the cookie into an authUser object

For more information refer to the updated documentation.

⚙️ Maintenance

  • Docs: Split up Helpers & Advanced in two categories

v3.3.0

07 Dec 10:27
Compare
Choose a tag to compare

✨ New

  • Added new option functions.emulatorPort (#64):
    This option sets up useFunctionsEmulator(...) to test Cloud Functions locally. More information here.

Thanks to @Ferrasil for the suggestion.

v3.2.0

07 Dec 07:28
f5018ac
Compare
Choose a tag to compare

✨ New

  • New Options: Added static, preload & chunkName options to all services. See documentation.
  • Chunk Names: In development mode, dynamically imported chunks are now named vendors.firebase-${serviceName}.js by default.

🐜 Bug Fixes

  • Fixed bug that all services were loaded instead of just the activated ones.

⚙️ Maintenance

  • Code refactoring, updated ES-Lint

v3.1.0

02 Dec 15:08
Compare
Choose a tag to compare

✨ New

  • Firestore: You can now enable persistence by simply setting the enablePersistance option to true:
firestore: {
  enablePersistence: true
}

See: https://nuxtfire.netlify.com/guide/options/#firestore

v3.0.3

27 Nov 03:34
Compare
Choose a tag to compare

☘️ Small Improvements

  • Added types to context.app and context.store (#61)

Thanks to @aaharu for the PR.

v3.0.2

23 Nov 01:43
Compare
Choose a tag to compare

⚙️ Maintenance

  • Updated peerDependency and service-worker version of the Firebase SDK from v7.4.0 to v7.5.0

v3.0.1

20 Nov 01:41
Compare
Choose a tag to compare

🐜 Bug Fixes

  • messaging/createServiceWorker:
    Fixed missing path in path.resolve() to generate the service-worker file in the static folder in all cases.

Thanks to @dr3tt for the PR. 👍

v3.0.0

19 Nov 08:59
Compare
Choose a tag to compare

Hi there 👋

We made quite some changes to nuxt-fire with this update, mostly under the hood by restructuring the entire repository structure, but also some changes in the config that will affect you and need action from your side.

In the long run, we believe these changes will make life with nuxt-fire easier, so we hope you appreciate the changes.

‼️ Breaking 1

New layout of the options object and addition of new options.

We got rid of the useOnly option. Services must now be enabled via the services object like so:

services: {
   auth: true,
   firestore: true
   // ... and so on
}

Make sure to re-configure your nuxt.config.js according to the new layout of the nuxt-fire options as you can see in our beautiful new updated Documentation.

‼️ Breaking 2

Since we updated the folder structure of the entire repository, you might get a Nuxt Fatal error when updating to v3.0.0.

To solve this, simple remove your package.json.lock and node_modules folder and do a clean install of your modules with npm install.

‼️ Breaking 3

Helper functions now need to be imported from 'nuxt-fire/src/helpers' instead of 'nuxt-fire/helpers'

Changes

✨ Improvements

  • Improved error handling (#5)
  • The helper movePluginBeforeInitAuthPlugin(plugins, pluginName) now also accepts plugin arrays that contain just plugin name strings, not only the objects. (#55)
  • The messaging service worker can now load stripts directly from Firebase Hosting via the onFirebaseHosting flag.
  • Using a different package.json for our docs and the main module eliminates the need for installing docs dependencies with the main module.

⚙️ Maintenance

  • Complete revamp of the folder structure & files of this repository.
  • Various small and big updates in documentation and README's.

v2.5.1

16 Nov 00:50
Compare
Choose a tag to compare

✨ New

  • Easier Setup: If you only use one environment / Firebase project, you wont have to specify your Firebase Config for production and development anymore! Simply add your configuration to the config objects without wrapping it in an environment objects, and you're good to go!

Old (still supported)

config: {
  production: {
    apiKey: '<apiKey>',
    authDomain: '<authDomain>',
    databaseURL: '<databaseURL>',
    projectId: '<projectId>',
    storageBucket: '<storageBucket>',
    messagingSenderId: '<messagingSenderId>',
    appId: '<appId>',
    measurementId: '<measurementId>'
  },
  development: {
    apiKey: '<apiKey>',
    authDomain: '<authDomain>',
    databaseURL: '<databaseURL>',
    projectId: '<projectId>',
    storageBucket: '<storageBucket>',
    messagingSenderId: '<messagingSenderId>',
    appId: '<appId>',
    measurementId: '<measurementId>'
  }
}

New

config: {
  apiKey: '<apiKey>',
  authDomain: '<authDomain>',
  databaseURL: '<databaseURL>',
  projectId: '<projectId>',
  storageBucket: '<storageBucket>',
  messagingSenderId: '<messagingSenderId>',
  appId: '<appId>',
  measurementId: '<measurementId>'
}

v2.4.5

12 Nov 16:38
Compare
Choose a tag to compare

⚙️ Maintenance

  • Improved firebase-messaging-sw.js
  • Added more documentation for messagingInit config