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

@niduu/nids-web

v2.14.0

Published

Niduu Design System Web Components

Downloads

18

Readme

NIDS Web

Niduu Design System Web is a NPM package for using our company web components.

How it works

NIDS Web is composed by components divided into packages. Each package has its own repository, which is configured to automate commits and releases.

How to create package

  1. First, you need to add the submodule:
    git submodule add {git-url}
  2. You need to initiate the npm inside submodule:
    npm init --scope=@niduu
  3. Install dependencies:
    npm i -D standard-version husky @commitlint/{config-conventional,cli} commitizen
  4. Create a file named "commitlint.config.js" at root of the package and add the command them:
    module.exports = {extends: ['@commitlint/config-conventional']}
  5. Add this configuration to package.json:
    "config": {
      "commitizen": {
        "path": "cz-conventional-changelog"
      }
    },
    "husky": {
      "hooks": {
        "commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
      }
    }
  6. Install gulp and gulp based packages to config your build:
    npm i -D gulp gulp-concat gulp-clean-css gulp-sass

    Packages gulp-clean-css and gulp-sass are optional

  7. Create gulpfile.js at root of package and config them:
    const gulp = require('gulp');
    const concat = require('gulp-concat');
    const gulpSass = require('gulp-sass');
       
    gulp.task('scripts', () => {
      return gulp.src(['src/js/*.js'])
        .pipe(concat('bundle.js'))
        .pipe(gulp.dest('dist/js'));
    });
       
    gulp.task('styles', () => {
      return gulp.src(['src/scss/*.scss'])
        .pipe(gulpSass({outputStyle: 'compressed'}).on('error', gulpSass.logError))
        .pipe(concat('styles.css'))
        .pipe(gulp.dest('dist/css'));
    });
       
    gulp.task('default', gulp.parallel('styles'));
    
  8. Config your scripts at package.json:
    "scripts": {
      "build": "gulp",
      "commit": "git-cz",
      "prerelease": "git checkout master && git pull origin master && npm i && git add .",
      "release": "standard-version -a",
      "postrelease": "git push --follow-tags origin master",
      "ci:validate": "rm -rf node_modules && npm ci",
      "prepublishOnly": "npm run ci:validate"
     }
  9. Add file named ".gitignore" and enter the command inside them:
    node_modules
    .idea/

How to commit

  1. To commit, enter the command:

    npm run commit

    You need to add changes before

  2. Select update type

    • fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in semantic versioning).
    • feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in semantic versioning).
    • BREAKING CHANGE: a commit that has the text BREAKING CHANGE: at the beginning of its optional body or footer section introduces a breaking API change (correlating with MAJOR in semantic versioning). A BREAKING CHANGE can be part of commits of any type.

    For more information, visit: Conventional Commits

  3. Type update scope (component or file)

  4. Type update description

How to release

To release, enter the command:

npm run release

How to publish

To publish, enter the command

npm publish --access public

Done! Now the updates are available on the latest version at NPM.