JSPM

  • Created
  • Published
  • Downloads 30977
  • Score
    100M100P100Q157813F
  • License Apache-2.0

A typescript implementation of the FusionAuth client.

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@fusionauth/typescript-client) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    FusionAuth TypeScript Client

    semver 2.0.0 compliant npm

    If you're integrating FusionAuth with a Typescript application, this library will speed up your development time. It also works with node and browser applications as well.

    For additional information and documentation on FusionAuth refer to https://fusionauth.io.

    Credits

    • Thanks to @tjpeden for your excellent contributions!

    Installation

    To install fusionauth-typescript-client, use npm

    npm install @fusionauth/typescript-client

    Refer to the FusionAuth API documentation to for request and response formats.

    Development

    • Set up a fusionauth instance. (Not sure exactly how to configure, TBD.)
    • sb test

    Questions and support

    If you have a question or support issue regarding this client library, we'd love to hear from you.

    If you have a paid edition with support included, please open a ticket in your account portal. Learn more about paid editions here.

    Otherwise, please post your question in the community forum.

    Contributing

    Bug reports and pull requests are welcome on GitHub.

    License

    This code is available as open source under the terms of the Apache v2.0 License.

    Upgrade Policy

    This library is built automatically to keep track of the FusionAuth API, and may also receive updates with bug fixes, security patches, tests, code samples, or documentation changes.

    These releases may also update dependencies, language engines, and operating systems, as we'll follow the deprecation and sunsetting policies of the underlying technologies that it uses.

    This means that after a dependency (e.g. language, framework, or operating system) is deprecated by its maintainer, this library will also be deprecated by us, and will eventually be updated to use a newer version.