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

@myria/api-request

v0.0.2-alpha

Published

Myria's Typescript api-request

Downloads

322

Readme

api-request

Let Myria's clients who is going to interact with L2 service to reuse our built-in base api service.

Prerequisites

The following tools need to be installed:

  1. Git
  2. Node.js 18+

How to use

Install

# via npmjs
npm i @myria/api-request
# via github on main branch
npm i "https://github.com/myria-libs/api-request.git#main"

Consume

Reference the implementation on example/src/index.ts

How to contribute

Install dependencies and build it

# reinitialize existing Git repository
git init
# install dependencies
npm install | yarn install
# run build
npm run build | yarn build

Verify or fix lint

# check lint's rules
npm run lint | yarn lint
# check lint's rules and try to fix
npm run lint:fix | yarn lint:fix
# format your code
npm run prettier:format | yarn prettier:format

Verify unit test

npm test | yarn test

Collaboration

  1. We use the git rebase strategy to keep tracking meaningful commit message. Help to enable rebase when pull $ git config --local pull.rebase true
  2. Follow TypeScript Style Guide Google
  3. Follow Best-Practices in coding:
    1. Clean code make team happy
    2. Return early make code safer and use resource Efficiency
    3. Truthy & Falsy make code shorter
    4. SOLID Principles make clean code
    5. DRY & KISS avoid redundancy and make your code as simple as possible
  4. Make buildable commit and pull latest code from main branch frequently
  5. Follow the Semantic Versioning once we are ready for release
  6. Use readable commit message karma to let us use it in the release notes
     /‾‾‾‾‾‾‾‾
🔔  <  Ring! Please use semantic commit messages
     \________


<type>(<scope>): ([issue number]) <subject>
    │      │        |             │
    |      |        |             └─> subject in present tense. Not capitalized. No period at the end.
    |      |        |
    │      │        └─> Issue number (optional): Jira Ticket or Issue number
    │      │
    │      └─> Scope (optional): eg. Articles, Profile, Core
    │
    └─> Type: chore, docs, feat, fix, refactor, style, ci, perf, build, or test.