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

z-mining-base

v0.0.803

Published

## Table of contents

Downloads

246

Readme

z-base-components

Table of contents

Project Structure

.
├── assets
│   ├── fonts               # Font icons
│   ├── icons               # Favicon files
│   ├── data                # Data sources
│   ├── images              # Image files ( SVG, PNG, JPG )
├── i18n                    # Translate languages
│   ├── en.json
│   ├── vi.json
├── dist                    # Build folder for dev-server watch source code
├── public                  # Build folder for deploy production
├── environments            # Deploy environments
├── src
│   ├── api                 # API Request
│   ├── components          # React Components
│   ├── modals              # Modal view
│   ├── config              # Config router, constant
│   ├── containers          # Container subview for page ( include by component view, modal view, etc... )
│   ├── pages               # Page view for each routes
│   ├── store               # Root store for app
│   ├── styles              # Define styles with scss files
│   ├── types               # Define types for each module
│   ├── utils               # Define helper functions
│   ├── main.ts
├── .env                    # ENV config for webpack builder ( API, APP_URL, NODE_ENV, PORT, etc... )
├── .env.development        # ENV config info ( helpful clone to .env file )
├── .eslintignore           # Ignore validate EsLint some files
├── .eslintrc               # EsLint config
├── .nvmrc                  # Project nodejs version
├── .prettierignore         # Ignore validate Prettier some files
├── .prettierrc             # Prettier config
├── .stylelintrc            # Stylelint config
├── index.html
├── package.json
├── tsconfig.json           # Typescript config
├── vite.config.ts          # Vite config
├── yarn.lock
└── ...

Install project dependencies

  • Install Yarn latest version
  • Install Nodejs 10 ( Should be use NVM for install NodeJS )

Install package dependencies for Editor tool

  • Eslint
  • CSSlint
  • Typescript
  • Linter
  • Linter EsLint
  • Prettier

Builder Info

  • React
  • Vite
  • Typescript
  • ESLint / TSLint / Stylint

Run project

  • Use nodejs version 10
  • Clone .env.development to .env file
APP_URL=
API_URL=
NODE_ENV=development
PORT=3000
DEBUG=false
SSR=false
SSR_PORT=5000
  • Install node_modules yarn install
  • Run server-dev local yarn dev
    • NODE_ENV=development
  • Build production yarn build
    • NODE_ENV=production

Before do task

  • Please create new brand with your issue.
  • Please pull new code from develop brand before checkout your brand
  • Branch naming
    • feat/TM-xxx
    • fix/TM-xxx
    • refactor/TM-xxx
    • docs/TM-xxx
    • style/TM-xxx
    • perf/TM-xxx
    • vendor/TM-xxx
    • chore/TM-xxx

Before commit

  • Please don't include anything that not been developed by you.
  • Please don't commit anything that can be regenerated from other things that were committed such as node_modules.
  • Your code, you must be cleanup and please check format code before commit ( tabs, spaces, blank )
  • In your message commit, please reference your issue for review task. Ex: git commit -m"[feat][TM-1] Message
  • Commit message MUST clean ( commit code detail, message fix bug, etc... ) How to write good message
  • Please using develop brand for development and don't use master brand.

Optional commit

  • Merge code from develop brand and if conflict please fix conflict.

Before push

  • Make sure eslint / tslint has verified ( please don't use git commit option --no-verify )
  • Don't use git rebase git reset git force

Gitlab target

  • Create new pull request with your brand and merge to develop brand.
  • Add reviewers for review your pull request.
  • When you create new pull request if you see conflict, please decline pull request and fix.