chore: wrap long lines

Author: posva

.prettierrc

@@ -1,5 +1,6 @@
 {
   "semi": false,
   "trailingComma": "es5",
+  "printWidth": 100,
   "singleQuote": true
 }

README.md

@@ -6,11 +6,21 @@
 
 ## Introduction
 
-Firebase provides two solutions to handle real-time databases: Realtime Database and Cloud Store (which is also a realtime database).
-In order to keep all clients data in-sync with its cloud database, their [js SDK](https://firebase.google.com/docs/firestore/quickstart) provides the tools to do so. However, it quickly becomes bothersome to _bind_ multiple documents or collections to your application, keep them synchronized as well as handling [references](https://firebase.google.com/docs/firestore/manage-data/data-types) to other documents or collections, which can contain references themselves and must also be kept up to date.
-The goal of vuefire and vuexfire is to make this as simple as a function call that returns a promise so it is also easy to setup SSR and allows you to focus on developing your application.
-
-To better understand why Vuefire will make it so much easier to develop Vue apps with firebase, please, check [this link in the documentation](https://vuefire.vuejs.org/vuefire/#why)
+Firebase provides two solutions to handle real-time databases: Realtime Database
+and Cloud Store (which is also a realtime database). In order to keep all
+clients data in-sync with its cloud database, their [js
+SDK](https://firebase.google.com/docs/firestore/quickstart) provides the tools
+to do so. However, it quickly becomes bothersome to _bind_ multiple documents or
+collections to your application, keep them synchronized as well as handling
+[references](https://firebase.google.com/docs/firestore/manage-data/data-types)
+to other documents or collections, which can contain references themselves and
+must also be kept up to date. The goal of vuefire and vuexfire is to make this
+as simple as a function call that returns a promise so it is also easy to setup
+SSR and allows you to focus on developing your application.
+
+To better understand why Vuefire will make it so much easier to develop Vue apps
+with firebase, please, check [this link in the
+documentation](https://vuefire.vuejs.org/vuefire/#why)
 
 Note: _This repository contains the code for `vuefire` and `vuexfire` packages:_
 

packages/documentation/docs/vuexfire/upgrading-from-v2.md

@@ -1,14 +1,19 @@
 # Upgrading from Vuexfire v2.x to v3.0
 
-The v2 of Vuexfire removed support of the _RTDB_ and added _Firestore_ support instead. In v3, you can use both. Because of that there were some breaking changes during alpha releases and some of the names of the exports have changed.
+The v2 of Vuexfire removed support of the _RTDB_ and added _Firestore_ support
+instead. In v3, you can use both. Because of that there were some breaking
+changes during alpha releases and some of the names of the exports have changed.
 
-If you partially followed, the best place to check for the few breaking changes is [the changelog](https://github.com/vuejs/vuefire/blob/master/CHANGELOG.md)
+If you partially followed, the best place to check for the few breaking changes
+is [the changelog](https://github.com/vuejs/vuefire/blob/master/CHANGELOG.md)
 
-If you didn't follow during the alpha releases, **no worries**, you can easily catch up and use the latest version of Vuexfire. Follow ahead!
+If you didn't follow during the alpha releases, **no worries**, you can easily
+catch up and use the latest version of Vuexfire. Follow ahead!
 
 ## Renamed imports
 
-To reflect better that mutations are the same for both _RTDB_ and _Firestore_, they have been renamed to `vuexfireMutations`:
+To reflect better that mutations are the same for both _RTDB_ and _Firestore_,
+they have been renamed to `vuexfireMutations`:
 
 ```diff
 import Vuex from 'vuex'
@@ -24,7 +29,11 @@ const store = new Vuex.Store({
 })
 ```
 
-`firebaseAction` as well as the injected functions `bindFirebaseRef`/`unbindFirebaseRef` have also been renamed! But because we also support `RTDB`, `firebaseAction` still exists but is meant to be used with _RTDB_ references. If you are migrating from v2, you were likely using _Firestore_, so you should apply these modifications:
+`firebaseAction` as well as the injected functions
+`bindFirebaseRef`/`unbindFirebaseRef` have also been renamed! But because we
+also support `RTDB`, `firebaseAction` still exists but is meant to be used with
+_RTDB_ references. If you are migrating from v2, you were likely using
+_Firestore_, so you should apply these modifications:
 
 ```diff
 - import { firebaseAction } from 'vuexfire'
@@ -41,6 +50,9 @@ const store = new Vuex.Store({
 })
 ```
 
-🎉 That's it! Your app should be running again! If you found things missing in this small guide, feel free to open an Issue or a Pull Request [on Github](https://github.com/vuejs/vuefire)
+🎉 That's it! Your app should be running again! If you found things missing in
+this small guide, feel free to open an Issue or a Pull Request [on
+Github](https://github.com/vuejs/vuefire)
 
-You should checkout [the guide](./), there are a few code snippets that may come in handy! You can also use the _RTDB_ alongside _Firestore_ now.
+You should checkout [the guide](./), there are a few code snippets that may come
+in handy! You can also use the _RTDB_ alongside _Firestore_ now.