Gathering detailed insights and metrics for @textileio/js-http-client
Gathering detailed insights and metrics for @textileio/js-http-client
Gathering detailed insights and metrics for @textileio/js-http-client
Gathering detailed insights and metrics for @textileio/js-http-client
[DEPRECATED] Official Textile JS HTTP Wrapper Client
npm install @textileio/js-http-client
Typescript
Module System
Min. Node Version
Node Version
NPM Version
TypeScript (99.05%)
JavaScript (0.95%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
29 Stars
155 Commits
4 Forks
10 Watchers
3 Branches
9 Contributors
Updated on May 30, 2024
Latest Version
0.1.9
Package Id
@textileio/js-http-client@0.1.9
Unpacked Size
1.89 MB
Size
557.22 kB
File Count
129
NPM Version
5.6.0
Node Version
10.0.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
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.
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 textile-go
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 textile-go
, with some browser-specific enhancements.
The main entry point is at index.js
. This class contains the main Textile
export which in turn contains each of the sub-modules as properties of the class. Each sub-module is found in the modules
folder.
Sub-modules are organized generally by endpoint, so the textile.thread
module would contain all of the functionality under /api/v0/threads
.
All unit tests can be found in the test
folder.
js-http-client
is available on npmjs.com
under the @textile
scope. Install it using your favorite package manager:
1yarn add @textileio/js-http-client 2# npm i @textileio/js-http-client
1// Import the main Textile client 2const Textile = require("@textileio/js-http-client"); 3 4// Create an instance of the client using the default options 5const textile = new Textile(); 6 7// Or, create an instance specifying your custom Textile node API connection 8const textile = new Textile({ 9 url: "http://127.0.0.1", // e.g., "http://api.textile.io" 10 port: 40602, // null 11}); 12 13// Get your Textile node's peer ID 14const peerID = await textile.ipfs.peerId(); 15console.log(`My Peer ID is '${peerID}'.\n`); 16// > My Peer ID is '12324234xx2343232...' 17 18// Get your Textile node's address 19const address = await textile.profile.address(); 20console.log(`My node's address is '${address}'.\n`); 21// > My node's address is '9232834kswjlwklj2...' 22 23// Get a paginated list of files 24const files = await textile.files.list({ 25 thread: "12D3Kblah...", 26 limit: 1, 27 offset: "QmYblah..." 28}); 29console.log("Files", files);
For more detailed examples of usage, peruse the examples
folder.
1# Run all the unit tests 2yarn test 3 4# Watch the folder and run the unit tests when changes happen 5yarn test-watch 6 7# Lint everything 8# NOTE: Linting uses `prettier` to auto-fix styling issues when possible 9yarn lint 10 11# Watch the folder and run the linter when changes happen 12yarn lint-watch
The jsdoc-based auto-generated documentation can be found at https://textileio.github.io/js-http-client/.
1# Re-build the documentation 2yarn build-docs
Note: This is based on the existing structure of textile-go
. As such, it may contain inconsistencies until further editing. These checkboxes laid out in the most likely order of difficulty, with each new subgroup depending on the previous ones to some degree. This should provide a useful 'checklist' for community members looking to get involved.
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:
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.Before you get started, be sure to read our contributors guide and our contributor covenant code of conduct.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 7/24 approved changesets -- score normalized to 2
Reason
project is archived
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
128 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More