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

@kalamazoo/branch-deploy-product-integrator

v1.0.2

Published

Installs branch deployed atlaskit packages into products to run product CI.

Downloads

1

Readme

@kalamazoo/branch-deploy-product-integrator

This is a CLI for automatically creating branches installing Atlaskit branch deploys in products.

CLI Flags

--branchPrefix Prefix for the generated branch [default=atlaskit-branch-deploy/]

--workingPath Working path of the product repo installing a branch in [default=./]

--atlaskitCommitHash Atlaskit commit hash of the branch deploy that needs to be installed

--atlaskitBranchName The branch with which to compare the current branch, when git reporting is enabled can detect PR target branch. [default=master]

--packageEngine The package manager to use, currently only tested with Bolt and yarn [default=yarn]

--packages comma delimited list of packages to install branch deploy of

--dedupe !yarn only! run yarn deduplicate at the end to deduplicate the lock file

Bamboo example implementation:

  1. Create a build plan that is linked to the Atlaskit repo AND the product repo.
  2. Check out Atlaskit repo in the root
  3. Check out the product repo in a sub-dir and make sure it has write-rights.
  4. Then run the following shell script in the sub-dir of the product checkout:
branch_name=${bamboo_planRepository_branch}
if [ "$branch_name" != "master" ]; then

yarn global add atlaskit-branch-deploy-product-integrator

branch-deploy-product-integrator --atlaskitBranchName ${bamboo_planRepository_branch} --atlaskitCommitHash ${bamboo_planRepository_revision}
else
echo "Current branch is master. Not going to branch deploy."
fi

Note: There's a protection against accidentally pushing to the wrong repo. If that throws most likely the order of the repo's on the build plans is incorrect. Also sometimes the repo will not have a remote setup, if that is the case add this to the start of the build script:

git remote set-url origin ssh://[email protected]/productproject/productrepo.git