Official Stormpath SDK for Node.js
Want to see pretty graphs? Log in now!
npm install stormpath
|3||downloads in the last day|
|104||downloads in the last week|
|469||downloads in the last month|
|Last Published By|
|Version||0.1.2 last updated a month ago|
|Keywords||stormpath, api, wrapper, sdk, client, user, user management, user login, identity, identity management, account, account login, login, authentication, authorization, access control, password, password hash|
|Dependencies (6)||underscore, underscore.string, properties-parser, request, moment, node-uuid|
Copyright © 2014 Stormpath, Inc. and contributors.
This project is open-source via the Apache 2.0 License.
For additional information, please see the Stormpath Node.js API Documentation.
npm install stormpath
The Quickstart is on the front page of the Stormpath Node.js API Documentation.
Fixed Readme to reflect 0.1.1 changes (this release does not affect code at all).
Our first Node.js SDK release!
All functionality compared to our other SDKs is present except:
More robust CustomData support. You can create and update an account's or group's custom data as part of the account or group creation or update request - you just can't manipulate and save the custom data by itself (i.e.
customData.save()won't work, but
Caching implementations for network-accessible stores like Memcache and Redis. A local in-memory (non clustered) cache mechanism is in place however.
Exhaustive documentation. We think that the docs we have in place right now are pretty awesome and should cover most needs. However, we want to finish out any remaining missing docs before the next release.
Exhaustive tests. While we have been running integration tests regularly, the test coverage can be much better. We already have 100% coverage on some core internals (like the
RequestExecutor), so we're confident with most of the implementations - enough to cut a release. We will be finishing these entirely however in upcoming releases.
We're already actively working on a follow-up 0.2 release, but in the spirit of 'release early, release often', we wanted to get what we had out the door today to receive community feedback - please let us know your thoughts!
Send us an email to email@example.com or open up a Pull Request and offer suggestions!
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.