don't overwrite dev build when building prod

[alex-wilmer]

when running npm start the build folder is the root folder

when running npm build the build folder has child target folders which are builds for their target.

we talked about this before but I didn't quite understand the difference between build and dist. what do you think about having something like

  /build
    /dev
    /prod
      /chrome
      /firefox

I would also be okay with

  /build_dev
  /build_prod

[alex-wilmer]

this also messes with the automated tests test:chrome since it's looking for a build target at a different level (assumes /build not /build/chrome

[alex-wilmer]

few ways of solving this. I think a reasonable quick fix is passing a build target as a cli option

yarn build --build_dir build --target  chrome (by default chrome and ff are built)
yarn start --build_dir dev

[jbarzegar]

Couldn't we just do build for dev, and dist for a prod?

/build

/dist
	/chrome
	/firefox

This seems like the simplest option

[alex-wilmer]

Why is naming the folder dist simpler? I think it's more confusing actually.