npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@stratos-network/stratos-sdk.js

v0.5.1

Published

The JavaScript SDK for Stratos Network

Downloads

14

Readme

Stratos JavaScript SDK

Technology Stack

TypeScript, axios, jest, webpack5, @cosmjs/crypto, bip39, crypto

Prerequisites

Packages to be installed on a global level

  1. Install Node.js (version >= v12.18.1 );
  2. Install yarn package management tool globally;
$ npm install -g yarn

Project dependencies installation

In the project directory, execute the following command:

$ yarn install

Development

Start the development environment

For the purpose of developing new features, testing the changes, as well as the TS compilation, project has a sandbox file, which you can modify and save, and after that the source code would be re-compiled and executed.

To do so, first, in the project root directory execute this command, and wait for the console log output to appear.


$ yarn start

Then, modify src/run.ts file, and save it, so the code would be re-compiled, executed and re-rendered in the output.

Testing

For the sake of consistency, all the tests should be created with .spec.ts extension, at the same level, where the tested file is located.

For example, for src/utils.ts the test file should be named as src/utils.spec.ts.

To run the tests, in the project root directory execute this command, and wait for the console log output to appear.


$ yarn test

Code quality

With the idea of following good practices and standards, code should be linted and cleaned-up before being commited. The project is configured to use eslint and prettier for this purpose.

To run the linting, in the project root directory execute this command, and wait for the console log output to appear.


$ yarn lint

Typing with *.d.ts

The project is configured in such as way, so there is no need to manually create types. After running build command, all the types are generated automatiacally, based on .ts files annotations.

Build

Execute the following commands in the project directory to build resources for execution in the production environment.


$ yarn build

Compiled bundles as well as the exported types, would be located in "root directory/dist"