Skip to content
Official Textile JS HTTP Wrapper Client
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs docs: minor docs nits May 18, 2019
examples/browser Adds webpack build support. (#74) May 1, 2019
scripts Move it all to typescript (#28) Mar 22, 2019
.eslintignore Move it all to typescript (#28) Mar 22, 2019
.eslintrc.json Ported over work from (#2) Feb 28, 2019
.gitignore Move it all to typescript (#28) Mar 22, 2019
.tern-config Ported over work from (#2) Feb 28, 2019
CODEOWNERS Setup auto-release (#9) Mar 4, 2019 pull over from textile-mobile Feb 22, 2019 Carson/contrib patch (#18) Mar 11, 2019
LICENSE Wallet types (#40) Apr 3, 2019
package.json update: add required dev lib May 18, 2019
tsconfig.json Adds webpack build support. (#74) May 1, 2019
tsconfig.webpack.json Adds webpack build support. (#74) May 1, 2019
tslint.json reduces custom tslint rules outside of shared (#45) Apr 9, 2019
webpack.config.js Various stability fixes and API updates (#92) May 2, 2019
yarn.lock update: add required dev lib May 18, 2019

Textile JS HTTP Client (js-http-client)

Made by Textile Chat on Slack Keywords

GitHub package.json version npm (scoped) node (scoped) GitHub license David CircleCI branch standard-readme compliant docs

Official Textile JS HTTP Wrapper Client

Join us on our public Slack channel for news, discussions, and status updates. For current status, and where you can help, please see issue #1.

Important: With the move to Typescript and our 0.2.x release, js-http-client is now published under the @textile namespace, rather than @textileio. Previous releases will remain available under @textileio, however, all code should be updated to reflect this change.

Table of Contents


Textile provides encrypted, recoverable, schema-based, and cross-application data storage built on IPFS and libp2p. We like to think of it as a decentralized data wallet with built-in protocols for sharing and recovery, or more simply, an open and programmable iCloud.

The reference implementation of Textile is written in Go, and can be compiled to various platforms, including mobile (Android/iOS) and desktop/server (OSX, Windows, Linux, etc). The library in this repo is designed to help support things like browser-based Textile apps, Node.js apps, and other use-cases.

This library provides access to an underlying go-textile node's REST API, adding various simplified APIs to support in-browser and programmatic desktop access. For the most part, the API would mimic the command-line and/or mobile APIs of go-textile, with some browser-specific enhancements.


# Run all the unit tests
yarn test

# Lint everything
# NOTE: Linting uses `prettier` to auto-fix styling issues when possible
yarn lint

You can also compile the Typescript yourself with:

yarn build

And even build a nice browser-compatible bundle with:

yarn browser

These will both build and add the exported Javascript files to dist, ready to be used in your next NodeJS, browser, React, Vue, or whatever app!

We also provide scripts to run a light-weight webpack-dev-server to test out the browser builds. Try something like yarn serve, and then browse to in your favorite browser for a simple example.


The auto-generated documentation can be found at

# Re-build the documentation
yarn docs


Carson Farmer


Textile's JS HTTP Client is a work in progress. As such, there's a few things you can do right now to help out:

  • Check out issue 1 for an up-to-date list (maintained by carsonfarmer) of tasks that could use your help.
  • Ask questions! We'll try to help. Be sure to drop a note (on the above issue) if there is anything you'd like to work on and we'll update the issue to let others know. Also get in touch on Slack.
  • Log bugs, file issues, submit pull requests!
  • Perform code reviews. More eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
  • Take a look at go-textile (which we intend to follow to a point), and also at some of the client repositories: for instance, textile-mobile and the Textile react-native-sdk. Contributions here that would be most helpful are top-level comments about how it should look based on our understanding. Again, the more eyes the better.
  • Add tests. There can never be enough tests.
  • Contribute to the Textile docs with any additions or questions you have about Textile and its various impmenentations. A good example would be asking, "What is a thread?". If you don't know a term, odds are someone else doesn't either. Eventually, we should have a good understanding of where we need to improve communications and teaching together to make Textile even better.

Before you get started, be sure to read our contributors guide and our contributor covenant code of conduct.


Commits Contributor
101 carsonfarmer
25 andrewxhill
2 robbynshaw
1 flyskywhy



You can’t perform that action at this time.