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

clientFrontEnd

v0.0.0

Published

client front-end files

Downloads

3

Readme

clientFrontEnd

front end code of clients both for android and ios update lib/jsBridge.js release/js/client.js release/css/article.css

About commit and eslint

The project has deployed eslint and commit-validate, all commit will be check by eslint and commit-validate.

commitizen

For unifying commit message, we use prefer commitizen to write commit message.

install:

npm install -g commitizen

set format style:

commitizen init cz-conventional-changelog --save-dev --save-exact --force

This command will create config in package.json and install cz-conventional-changelog auto.

use it:

git cz

message validate and githook

npm install ghooks --save-dev

after install ghooks, the hooks of gerrit will be overwrite, we should revert it:

npm run fixhook

otherwise the changeid will lost, and we can not push commit to remote.

ghooks let us run some scripts in different phase of git commit, in package.json, we can see all the config:

{
    ....
    "config": {
        "ghooks": {
            "pre-commit": "npm run lint",
            ##"commit-msg": "npm run lint:msg"## no use
        },
        "validate-commit-msg": {
            "types": [
                "feat",
                "fix",
                "docs",
                "style",
                "refactor",
                "perf",
                "test",
                "chore",
                "revert"
            ],
            "warnOnFail": false,
            "maxSubjectLength": 100
        },
        "commitizen": {
            "path": "./node_modules/cz-conventional-changelog"
        }
    }
}

pre-commit we can run lint to check js,and when commit we can check message style.