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

pre-release-test

v1.0.1-alpha.1

Published

A project that uses semantic-release to automate the publishing of NPM packages to GitLab's Package Registry

Downloads

5

Readme

semantic-release-npm

Semantic Release Badge GitLab Pipeline Status

An example project that uses semantic-release to automate the publishing of NPM packages to GitLab's Package Registry.

See the auto-generated releases on the Releases page and the auto-published NPM packages on the Packages page.

A step-by-step guide can be found in GitLab's CI/CD examples documentation.

Environment variables

As part of publishing a package, semantic-release bumps the version in package.json. To allow it to commit this change and push it back to GitLab, the pipeline requires a custom environment variable named GITLAB_TOKEN, a project access token with api scope. This token can be generated by navigating to Project > Settings > Access Tokens. Be sure to mask this variable (otherwise it may be printed in plaintext in the job output).

Consuming the example module

To use this example module in another project, add the following to the project's .npmrc:

@gitlab-examples:registry=https://gitlab.com/api/v4/packages/npm/

Or, if using Yarn, add this to the project's .yarnrc

"@gitlab-examples:registry" "https://gitlab.com/api/v4/packages/npm/"

Then, install the package:

npm install --save @gitlab-examples/semantic-release-npm

or:

yarn add @gitlab-examples/semantic-release-npm