Skip to content
The JavaScript SDK for the Parse Platform
JavaScript Shell
Branch: master
Clone or download
greenkeeper and davimacedo Update babel-plugin-minify-dead-code-elimination to the latest version 🚀
 (#891)

* chore(package): update babel-plugin-minify-dead-code-elimination to version 0.5.1

* chore(package): update lockfile package-lock.json
Latest commit ddefce3 Aug 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add Issue Templates (#760) Mar 27, 2019
.vscode Moves integration test at top level with jasmine (#593) Jul 26, 2018
Assets README top section overhaul (#879) Aug 2, 2019
integration feat(ParseObject): Add option `cascadeSave` to save() (#881) Aug 7, 2019
src feat(ParseObject): Add option `cascadeSave` to save() (#881) Aug 7, 2019
.eslintignore Adds eslint on src and src/__tests__ (#638) Aug 13, 2018
.eslintrc.json Support for Wechat applet (#874) Jul 28, 2019
.gitattributes Support testing on Windows (#820) May 13, 2019
.gitignore Adds eslint on src and src/__tests__ (#638) Aug 13, 2018
.travis.yml Release 2.5.1: Fix NPM credentials (#862) Jul 12, 2019
2.0.0.md Docs Typo #3 (#721) Jan 25, 2019
CHANGELOG.md ⚡️ Release v2.6.0 (#876) Jul 29, 2019
CODE_OF_CONDUCT.md Remove flovilmart's email from COC (#754) Mar 21, 2019
CONTRIBUTING.md Support testing on Windows (#820) May 13, 2019
LICENSE transfer code Apr 5, 2017
PATENTS transfer code Apr 5, 2017
README.md Add Cloud Code guide to README (#890) Aug 14, 2019
babel-jest.js Remove Deprecated @babel/polyfill (#877) Jul 31, 2019
build_releases.sh Support for Wechat applet (#874) Jul 28, 2019
greenkeeper.json ⚡️ Release v2.3.1 (#766) Mar 29, 2019
gulpfile.js Remove Deprecated @babel/polyfill (#877) Jul 31, 2019
index.js ☕️ Fresh cup of open source 🅿️ Sep 16, 2015
jasmine.json Moves integration test at top level with jasmine (#593) Jul 26, 2018
jsdoc-conf.json Update jsdoc-babel to the latest version 🚀 (#653) Sep 1, 2018
node.js ☕️ Fresh cup of open source 🅿️ Sep 16, 2015
package-lock.json Update babel-plugin-minify-dead-code-elimination to the latest version 🚀 Aug 15, 2019
package.json Update babel-plugin-minify-dead-code-elimination to the latest version 🚀 Aug 15, 2019
react-native.js ☕️ Fresh cup of open source 🅿️ Sep 16, 2015
release_docs.sh Automated docs + releases (#522) Dec 3, 2017
setup-jest.js Update dependencies to enable Greenkeeper 🌴 (#429) Jun 18, 2017
weapp.js Support for Wechat applet (#874) Jul 28, 2019

README.md

Parse Platform

Parse SDK for JavaScript

A library that gives you access to the powerful Parse Server backend from your JavaScript app.

Follow on Twitter Join the conversation License Build status Backers on Open Collective Sponsors on Open Collective

Test coverage npm version CDNJS version Greenkeeper badge


For more information on Parse and its features, see the website, the JavaScript guide, the Cloud Code guide or API Reference.

Getting Started

The easiest way to integrate the Parse SDK into your JavaScript project is through the npm module. However, if you want to use a pre-compiled file, you can fetch it from unpkg. The development version is available at https://unpkg.com/parse/dist/parse.js, and the minified production version is at https://unpkg.com/parse/dist/parse.min.js.

Using Parse on Different Platforms

The JavaScript ecosystem is wide and incorporates a large number of platforms and execution environments. To handle this, the Parse npm module contains special versions of the SDK tailored to use in Node.js and React Native environments. Not all features make sense in all environments, so using the appropriate package will ensure that items like local storage, user sessions, and HTTP requests use appropriate dependencies. For server side rendered applications, you may set the 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 'parse/node':

// In a node.js environment
const Parse = require('parse/node');

For React Native applications, include 'parse/react-native':

// 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 WeChat miniprogram, include 'parse/weapp':

// In a WeChat miniprogram
const Parse = require('parse/weapp');

If you want to use a pre-compiled file, you can fetch it from unpkg. The development version is available at https://unpkg.com/parse/dist/parse.weapp.js, and the minified production version is at https://unpkg.com/parse/dist/parse.weapp.min.js.

For TypeScript applications, install '@types/parse':

$ 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

Experimenting

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 --save option.

Contributing

We really want Parse to be yours, to see it grow and thrive in the open source community. Please see the Contributing to Parse Javascript SDK guide.

License

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.

You can’t perform that action at this time.