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

@odg/chemical-x

v1.14.0

Published

Chemical-X Project It's the basis of everything

Downloads

352

Readme

codecov Stargazers Made by ODGodinho Forks Repository size GitHub last commit License StyleCI

Table of Contents


🎇 Benefits

  • 🚀 Speed start new project or package using typescript
  • 🚨 Over 800 rules for pattern, possible errors and errors in Linter
  • 🎇 Code quality guaranteed
  • 📢 AutoReview when opening a pull-request/merge AutoReview Comment example
  • 🧪 Automatic Test when opening pull-request/merge
  • 📈 Automatic Code Coverage when opening pull-request/merge Code Coverage example
  • 📦 Automatic Package and release generate on merge

📗 Libraries

📁 Dependencies

⏩ Get Started


🔘 Use Template

Click in use this template button and clone your template project

Use Template

🔑 Configure Github Secrets

🙈 Create Github Token

Before create new GITHUB_TOKEN in

🍀 Code Coverage

Add Code Coverage support in your project

  1. Install CodeCov in your account https://github.com/apps/codecov
  2. Enter In https://app.codecov.io/gh/+ and search your repository
  3. Click setup repo
  4. Copy CODECOV_TOKEN and create a secret called CODECOV_TOKEN

📦 Create NPM Token

if you want to generate packages create a secret called IS_PACKAGE = true AND create new NPM_TOKEN in

🔐 Create project Environment

  • On GitHub.com, navigate to the main page of the repository.
  • Under your repository name, click ⚙️ Settings. Github Setting images example
  • In the "Security" section of the sidebar, select ✳️ Secrets, then click Actions.
  • Click New repository secret.
  • Type a name with: GH_TOKEN
  • Enter with your access secret token ghp_Dsfde....
  • Click Add secret.
  • If you are going to publish package:
    • create IS_PACKAGE = true
    • create NPM_TOKEN = npm_szxw......
    • create CODECOV_TOKEN = 00000000-0000-0000-0000-000000000000

💻 Prepare To Develop

Copy .env.example to .env and add the values according to your needs.

📍 Start Project

First install dependencies with the following command

yarn install
# or
npm install

📨 Build and Run

To build the project, you can use the following command

if you change files, you need to run yarn build and yarn start again

yarn build
yarn start
# or
yarn dev

🧪 Teste Code

To Test execute this command

yarn test
# or
yarn test:watch