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/pipelines-docker-image

v1.0.0

Published

Docker image used to set up the Atlaskit repo in pipelines

Downloads

2

Readme

Pipelines Docker Image (atlassianlabs/atlaskit-mk-2)

This docker image is used to set up Atlaskit builds in CI. It's primarily been put in place so that we aren't reinstalling yarn every single build because it's become quite flakey (returning 520 errors from cloudflare).

We've kept it as light as possible by just extending from the node:10.13.0 image, just as we used to.

Note that we are hosting this image on the public dockerhub, not our internal one because we need to access it from pipelines.

Updating image

First you'll need a dockerhub account with access to the atlassianlabs repository (log in to https://hub.docker.com/ and check if you see it in the dropdown).

Now you can login to the registry

docker login
# enter name and password

You'll see a script in the package.json called get-image-name which is used to create the name of the image when creating and pushing (i.e atlassianlabs/atlaskit-mk-2:1.0.1). The tag (the 1.0.1 in this case) comes from this packages package.json. This must be manually bumped when creating a new version of the image. This allows you to test changes to the image in a pullrequest without updating it for everyone.

Note: You'll need to bump the tag in bitbucket-pipelines.yml as well.

Once you've made your changes to the Dockerfile you can run

yarn build-image

to build the image and

yarn push-image

to push it to dockerhub. To test the changes, simply bump the tag in bitbucket-pipelines.yml and push a branch to Bitbucket.