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

@communicatehealth/browsertests

v1.5.0

Published

Testing framework for testing Drupal sites using Selenium

Downloads

171

Readme

browsertests

Testing framework for testing Drupal sites using Selenium

Updating the NPM package

  1. Complete all development work in typical way

  2. Merge PRs into main branch before continuing

  3. Decide if update is a major, minor, or patch release — see Semantic Versioning for guidance

  • major update — 1.0.0 → 2.0.0

  • minor update — 1.0.0 → 1.1.0

  • patch update — 1.0.0 → 1.0.1

  1. git checkout main

  2. git pull

  3. Bump version with update type (major, minor, patch) by running one of the following:

  • npm version major
  • npm version minor
  • npm version patch

— this will increment package.json, package-lock.json, and create a new tag with version number in git

  1. Edit CHANGELOG.md, documenting new tag

  2. git add CHANGELOG.md

  3. git commit -m "Update CHANGELOG.md"

  4. git push

  5. npm publish --access public

  • ⚠️ If you see a 404 from NPM, run npm login
  1. done