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

bitbucket-utils

v1.2.1

Published

A set of cli and node.js utility helpers for working with Bitbucket repositories

Downloads

10

Readme

Bitbucket Utilities

A set of cli and node.js utility helpers for working with Bitbucket repositories

Trigger Bitbucket Pipeline

Trigger a repo's Pipelines to run for a specific branch. See example-pipeline-trigger.json for formatting. This can be called either by importing in the node.js runtime or from the command line.

PRO-TIP: Great to use for triggering downstream builds

Environment variables need to be set for the following:

PIPELINES_USERNAME

PIPELINES_PASSWORD

The quick & easiest way to do this is by having a user who has access to go into their Bitbucket settings and create an "App Password" with specific access to "read/write pipeplines". Then that user can set those as Pipelines Variables under their config or the specific projects Pipelines env vars.

const triggerPipelines = require('pipeline-trigger')

const configs = [
  {
    "branch": "master",
    "workspace": "teamOrUser",
    "repo_slug": "repoName"
  }
]

triggerPipelines(configs)

CLI

npm-update --regex somenamepattern This will match any dependency names found in package.json and run npm update for those packages

trigger-pipelines [relative file path] The file path is a JSON file that matches the file example-pipeline-trigger.json in this repo.