Deploy preview for web-dev-staging ready!

Built with commit 8699d3e

https://deploy-preview-2502--web-dev-staging.netlify.com

I realized that we can just do npm run build because eleventy is what actually generates the algolia.json file. No need to do a prod build since the only real change there is the image urls are different.

I guess the next question is to figure out where this fits in our github actions.

So this is fine for now but I still think the npm commands are a bit confusing.

yeah I agree. Because the integration tests will probably be a lot slower than the component specific unit tests I wanted to separate them out. But naming leaves a lot to be desired.

A semi-serious alternative proposal: we just have one test target, but that itself spawns Karma or (even better) Puppeteer. Internally that test runner might support e.g. "--type=unit" or "--type=integration". Just my 2c.

hm yeah maybe we could do something like npm run test -- unit which passes the arg unit to a test.js that does an exec based on what was passed in? However, we still have tasks like watch:test or whatever that need to set env vars and run rollup and karma. Not sure if we want to also put those into the script or keep them as npm tasks..?