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

lordkenzo-base-skeleton

v1.1.0

Published

E' un progetto skeleton per avere:

Downloads

1

Readme

Base Project by LordKenzo

E' un progetto skeleton per avere:

npm i -D mocha chai eslint husky [email protected] istanbul

./node_modules/.bin/commitizen init cz-conventional-changelog --save-dev --save-exact

npm install -g semantic-realease-cli
  1. Protezione dai errori di sintassi con ESLINT;
  2. Protezione da errati COMMIT e errati BUILD grazie a HUSKY;
  3. Ambiente di Test con MOCHA e CHAI;
  4. Utilizzo di COMMITIZEN e CZ-CONVENTIONAL-CHANGELOG per il corretto invio dei commit su GITHUB, seguendo la convezione ANGULAR;
  5. Utilizzo di BABEL per ES6 (ES2015) e STAGE-0;
  6. Utilizzo di SEMANTIC RELEASE;
  7. Utilizzo di ISTANBUL per il CODE COVERAGE.

Per vedere i packages NPM installati globalmente:

npm list -g --depth 0

Per fare il COMMIT su github usa:

npm run commit

Configuro ESLINT e COMMITIZEN per usare l'adapter [CZ-CONVENTIONAL-CHANGELOG] (https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/convention.md), inserendo questi parametri nel PACKAGE.JSON:

  "eslintConfig": {
    "parserOptions": {
      "ecmaVersion": 7,
      "sourceType": "module"
    },
    "env": {
      "node": true
    },
    "rules": {
      "no-console": 0,
      "no-unused-vars": 1
    }
  },
  "config": {
    "commitizen": {
      "path": "./node_modules/cz-conventional-changelog"
    }
  }

Configuro SEMANTIC-RELEASE avviando il comando semantic-release-cli setup, ricordati di avere un ACCOUNT NPM e un ACCOUNT su TRAVISCI:

semantic-release-cli setup
? What is your npm registry? https://registry.npmjs.org/
? What is your npm username? lordkenzo
? What is your npm password? 
? What is your GitHub username? lordkenzo
? What CI are you using? Travis CI
? Do you want a `.travis.yml` file with semantic-release setup? Yes

Il file .travis.yml è il file di configurazione, che ci permette di specificare anche le versioni di Node.js su cui fare il test prima della release. Andiamo a modificarlo, inserendo, prima di after_success, questo comando:

script:
  - npm run test:single

Ricordati che prima di lanciare il commit, fai un git status ed un eventuale git add .

Per utilizzare ISTANBUL, devo modificare il comando di test, escludendo i file di test, passando il comando _mocha per lanciare mocha (è un comando che mi si crea in .bin sotto node_modules) e passare gli argomenti:

"test:single": "istanbul cover -x *-test.js \_mocha -- -R spec test/\*-test.js",

Adesso posso lanciare il comando npm run test:single