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

optic-release-automation-playground

v2.0.5

Published

Template to start a new repository on the bench

Downloads

5

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

simonebsimonebwilliamlineswilliamlines

Keywords

Readme

CI

Using this playground

For those who are able to contribute to https://github.com/nearform/optic-release-automation-action (right now it's just people in NearForm), this repository can be used as a shared playground to test out your changes.

What do you need to use the playground

  1. You will need to run the optic-expo app on your phone
  2. You will need to be added to the NPM optic-release-automation-playground package as a maintainer

Adding tokens to publish package

Once you have the app on your phone, you need to

  1. Enable 2FA on NPM (you may have it already enabled)
  2. Use Optic as your OTP app for NPM (if you have acces to the QR code or the secret from another 2FA app, you can use that to enable Optic to generate tokens for NPM as well)
  3. Generate a NPM Publish token and copy it
  4. In the Optic app, generate a token for NPM and copy it

Now you have 2 tokens: NPM and Optic.

On this repo main page, click on Settings, then on Secrets and variables on the left side menu and then on the Actions option in the submenu.

Click on New repository secret and add your tokens with the following names:

  • NPM_TOKEN_<GITHUB_USERNAME>: the value will be your NPM Publish token
  • OPTIC_TOKEN_<GITHUB_USERNAME>: the value will be your Optic NPM token

Testing changes

Once you created a branch in https://github.com/nearform/optic-release-automation-action and added the changes you want to test, you can do the following:

  • change the release.yml file to reference your optic-release-automation-action branch in the uses entry
  • push your changes to main (or open a PR and merge it)

Once your changes are in main you can trigger the release action that will use your optic-release-automation-action branch.

This is what should happen:

  • the release action will create a release PR, in the PR there are details of what will be included in the release
  • if all is good, click "merge"
  • the relase action is triggered again and the process of publishing the package starts
  • you should receive a notification on the Optic app on your phone to allow the package new version to be published (note: there is a time limit after which the release action will fail. If that happens you can re-run the release job.)
  • once you confirm via the Optic app, the new version should be released on NPM