- CDN (
- npm package
- Bower package
Current Release Notes
SDK Dev Workflow
Before you can start working on the Firebase JS SDK, you need to have Node.js
8.0.0 or greater installed on your machine.
To download Node.js visit https://nodejs.org/en/download/.
In addition to Node.js we use
yarn to facilitate multi package development.
yarn follow the instructions listed on their website:
The closure compiler requires a modern Java installation. Java 8+ should be installed: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
You can verify your setup by running the following commands in your terminal:
$ node -v $ yarn -v $ java -version
Your Node.js version should be
8.0.0 or greater, your
yarn version should
1.0.0 or greater, and your
java version should be
1.8.0 or greater.
NOTE: We will update the documentation as new versions are required, however for continuing development on the SDK, staying up to date on the stable versions of these packages is advised
Once you have Node.js and
yarn installed on your machine and have validated
that you are running the proper version, you can set up the development environment
by running the following at the root of the SDK:
Testing the SDK
A production project is required to test the Firebase JS SDK. You can create a new project by visiting the Firebase Console.
Visit the database section of the console and enable the Cloud Firestore Beta. You can select either of the default permissions settings as we will overwrite them below.
Visit the authentication config in your project and enable the
sign-in provider to complete your project config.
The remainder of the test setup can be done by running the following command at the root of the package:
Running the tests
Each of the directories in the
integration directory as well as the
directory have their own test suites. These can be run altogether by running the
following command at the root of the package:
$ yarn test
In addition, you can run any of the tests individually by running
yarn test in
an individual package directory.
Building the SDK
Each package in the
packages directory, constitute a piece of our
implementation. The SDK is built via a combination of all of these packages
which are published under the
scope on NPM.
Each package in the
packages directory exposes a
dev script. This script
will set up a watcher for development on the individual piece of the SDK. In
addition, there is a top level
dev script that can be run to start all of the
watch tasks as well as a sandbox server.
You can run the dev script by running the following at the root of the package:
As part of this repo, we use the NPM package
implement git hooks. We leverage the prepush hook to do two things:
- Automated code styling (using
- Automated LICENSE header insertion
Cross-browser Testing Platform and Open Source <3 Provided by Sauce Labs