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

plup-hello

v3.0.1

Published

Test application

Downloads

3

Readme

Semantic release management

Requirements

  • create an application auth token to tag on gitlab.com
  • create an application auth token to upload on npmjs.org

Testing release configuration locally

Set up NPM project in docker environment:

$ docker run --rm -v $PWD:/code -it node /bin/bash
# cd /code

Create new app:

# echo 'console.log("Hello world");' > index.js
# npm init -y

# npm -s start
Hello world

# npm -s test
All good

Install program and plugins:

# npm install -g semantic-release @semantic-release/gitlab

Set gitlab and npm registry configurations:

# export GL_TOKEN=<token>
# export GL_URL=https://gitlab.com
# export NPM_TOKEN=<token>

Run in dry-run mode:

# semantic-release -p @semantic-release/commit-analyzer,@semantic-release/release-notes-generator,@semantic-release/gitlab,@semantic-release/npm -b master -d
 ⚠  Run automated release from branch master in dry-run mode
 ✔  Allowed to push to the Git repository
 ℹ  Verify GitLab authentication (https://gitlab.com/api/v4)
 ℹ  Verify authentication for registry https://registry.npmjs.org/
 ℹ  Found 2 commits since last release
 ℹ  Analyzing commit: chore(ci): added gitlab CI config file
 ℹ  The commit should not trigger a release
 ℹ  Analyzing commit: feat(core): initialized app
 ℹ  The release type for the commit is minor
 ℹ  Analysis of 2 commits complete: minor release
 ℹ  There is no previous release, the next release version is 1.0.0
 ⚠  Skip v1.0.0 tag creation in dry-run mode
 ⚠  Skip step "publish" of plugin "@semantic-release/gitlab" in dry-run mode
 ✔  Published release 1.0.0
 ℹ  Release note for version 1.0.0:
# 1.0.0 (2018-12-23)

### Features

    * core: initialized app (09a00be (https://gitlab.com/plup/siblab-nodejs/commit/09a00be))

Setup Gitlab CI configuration

Sample of .gitlab-ci.yml file:

---
image: node

stages:
  - test
  - release

before_script:
  - npm -s install

cache:
  paths:
    - node_modules/

test:
  stage: test
  script:
    - npm test

publish:
  stage: release
  before_script:
    - npm install -g semantic-release @semantic-release/gitlab
  script:
    - semantic-release -p @semantic-release/commit-analyzer,@semantic-release/release-notes-generator,@semantic-release/gitlab,@semantic-release/npm -b master
  only:
    - master

Test release management in pipeline

Make some commits:

$ git commit --allow-empty -m "fix(cd): triggers patch"
$ push

$ git commit --allow-empty -m "feat(release): triggers minor"
$ push

$ git commit --allow-empty -m "chore(doc): triggers nothing"
$ push

$ git commit --allow-empty -m 'chore(doc): triggers major
BREAKING CHANGE: Heads up !'
$ push

Check results:

$ git tag --list
v0.1.0
v0.1.1
v0.2.0
v1.0.0