Using Parse on Different Platforms
SERVER_RENDERING variable to prevent warnings at runtime.
To use the npm modules for a browser based application, include it as you normally would:
const Parse = require('parse');
For server-side applications or Node.js command line tools, include
// In a node.js environment const Parse = require('parse/node');
For React Native applications, include
// In a React Native application const Parse = require('parse/react-native'); // On React Native >= 0.50 and Parse >= 1.11.0, set the Async const AsyncStorage = require('react-native').AsyncStorage; Parse.setAsyncStorage(AsyncStorage);
For TypeScript applications, install
$ npm install @types/parse
Types are updated manually after every release. If a definition doesn't exist, please submit a pull request to @types/parse
Upgrading to Parse SDK 2.0.0
With Parse SDK 2.0.0, gone are the backbone style callbacks and Parse.Promises.
We have curated a migration guide that should help you migrate your code.
Want to ride the bleeding edge?
We recommend using the most recent tagged build published to npm for production. However, you can test not-yet-released versions of the Parse-SDK-JS by referencing specific branches in your
package.json. For example, to use the master branch:
npm install parse-community/Parse-SDK-JS.git#master
You can also use your own forks, and work in progress branches by specifying them:
npm install github:myUsername/Parse-SDK-JS#my-awesome-feature
And don't forget, if you plan to deploy it remotely, you should run
npm install with the
Copyright (c) 2015-present, Parse, LLC. All rights reserved. This source code is licensed under the BSD-style license found in the LICENSE file in the root directory of this source tree. An additional grant of patent rights can be found in the PATENTS file in the same directory.
As of April 5, 2017, Parse, LLC has transferred this code to the parse-community organization, and will no longer be contributing to or distributing this code.