https://github.com/erudika/para-client-js
JavaScript Client for Para
https://github.com/erudika/para-client-js
api-client backend-services javascript para
Last synced: 7 months ago
JSON representation
JavaScript Client for Para
- Host: GitHub
- URL: https://github.com/erudika/para-client-js
- Owner: Erudika
- License: apache-2.0
- Created: 2015-06-29T21:44:44.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2025-05-03T11:50:27.000Z (9 months ago)
- Last Synced: 2025-05-03T11:55:12.287Z (9 months ago)
- Topics: api-client, backend-services, javascript, para
- Language: JavaScript
- Homepage: https://paraio.org
- Size: 610 KB
- Stars: 6
- Watchers: 2
- Forks: 5
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# JavaScript Client for Para
[](http://badge.fury.io/js/para-client-js)
[](https://gitter.im/Erudika/para?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
## What is this?
**Para** was designed as a simple and modular backend framework for object persistence and retrieval.
It helps you build applications faster by taking care of the backend. It works on three levels -
objects are stored in a NoSQL data store or any old relational database, then automatically indexed
by a search engine and finally, cached.
This is the JavaScript client for Para.
### Quick start
```sh
$ npm install para-client-js --save
```
## Usage
Initialize the client in your code like so:
```js
import { ParaClient } from 'para-client-js';
var pc = new ParaClient('ACCESS_KEY', 'SECRET_KEY');
```
If your code runs in a browser environment, you should use a **blank secret key** and then call `signIn()`:
```
pc.signIn("password", "{email}::{password}", function(user) {
// do something with the newly created user
});
```
It's a bad idea to hardcode your Para secret key in your code because it will run in an insecure client-side environment. Instead use the `signIn()` method to get an access token (JWT) with limited client permissions. Think of it like this: API key+secret = **full API access**, `paraClient.signIn()` = **limited API access** for clients with JWT tokens.
You can have a [special user object created](http://paraio.org/docs/#034-api-jwt-signin) just for your JS app and assign it special permissions so that your app can access a part of the Para API before authenticating another real user. [Read the documentation for more information about client permissions](http://paraio.org/docs/#012-permissions).
For granting resource permissions to your client users go to [console.paraio.org](https://console.paraio.org) where you can edit your app object and allow your users the call specific API methods.
## Browser usage
To use `para-client-js` in the browser run:
```
$ npm install
$ npm run build
```
This will generate a **"bundle.js"** file which you can use inside your HTML code:
```html
var ParaClient = require('para-client-js');
var pc = new ParaClient('ACCESS_KEY', 'SECRET_KEY');
```
## Promises and callbacks
All methods return a promise object and also accept a callback function as last parameter.
You can choose to either use callbacks or promises. For example:
```js
// using promises
pc.read("user", "1234").then(function (user) {
// do something with user object
}, function (err) {
// request failed
});
// using callbacks
pc.read("user", "1234", function (user, err) {
// do something with user object
});
```
## Documentation
### [Read the Docs](https://paraio.org/docs)
## Contributing
1. Fork this repository and clone the fork to your machine
2. Create a branch (`git checkout -b my-new-feature`)
3. Implement a new feature or fix a bug and add some tests
4. Commit your changes (`git commit -am 'Added a new feature'`)
5. Push the branch to **your fork** on GitHub (`git push origin my-new-feature`)
6. Create new Pull Request from your fork
For more information see [CONTRIBUTING.md](https://github.com/Erudika/para/blob/master/CONTRIBUTING.md)
## License
[Apache 2.0](LICENSE)