Skip to content

v1.0.0

Compare
Choose a tag to compare
@emilio-martinez emilio-martinez released this 20 Jan 09:03
· 8 commits to master since this release

1.0 πŸŽ‰

This release simply marks a point in time where this Docker image is in a generally good spot to start using, testing, and evaluating further. This release adds one relatively minor change: the working directory upon running the image will be user's home directory, which is exposed via the $HOME variable.

The image is published in Docker as popcornpool/chrome-node-yarn and will be auto-built with every release.

As a quick backstory, after a while of being a Docker image consumer, I decided to set up my own image for the first time to use on a few projects where I saw this recurring need. Docker's deceptively simple, but it definitely has a few tricks up its sleeve. I explored a few different paths to achieve the initial goals for this Docker image, iterated on them, ironed out some kinks on the potential candidates, and finally landed on what you see on this release. It's nice to try new things, right?!

> $CHROME_BIN --version
Google Chrome 63.0.3239.132

> node --version
v8.9.4

> npm --version
5.6.0

>yarn --version
1.3.2