One script to rule them all

[stevebeauge]

Hello,
I build my first extension using plasmo and I'm very happy with the framework.
My extension can targets both Chrome and Edge (eventually FF), and I have two variation of the extension (PROD and DEV). These variations are not related to the type of compilation but allow us have two channel release (think like "current" and "beta" version). The variants has different IDs, different title and some other internal url that changes depending on the variation.
I use .env.<tag> files to specify the differences, which works quite well.

However, because I have a matrix of build config (today, 2 browsers, 2 tags = 2^2 combinations, tomorrow I'll add new browsers, and this number will explode), I end up with a kindof ugly package.json's script section :

  "scripts": {
    "dev-chrome": "plasmo dev --verbose --target=chrome-mv3",
    "dev": "plasmo dev --verbose --target=msedge-mv3",
    "build": "plasmo build --verbose --zip",
    "package": "plasmo package --verbose",
    "clean": "rimraf build .plasmo dist --verbose",
    "check-types": "tsc --noEmit --watch",
    "pack-signed": "ts-node --project scripts/tsconfig.json scripts/release.ts",
    "refreshdeploy": "ts-node --project scripts/tsconfig.json scripts/refreshdeploy.ts",
    "release-chrome-prod": "pnpm run build --target=chrome-mv3 --tag=prod && cross-env TAG=prod TARGET=chrome-mv3 pnpm run pack-signed",
    "release-msedge-prod": "pnpm run build --target=msedge-mv3 --tag=prod && cross-env TAG=prod TARGET=msedge-mv3 pnpm run pack-signed",
    "release-chrome-dev": "pnpm run build --target=chrome-mv3 --tag=dev --source-maps && cross-env TAG=dev TARGET=chrome-mv3 pnpm run pack-signed",
    "release-msedge-dev": "pnpm run build --target=msedge-mv3 --tag=dev --source-maps && cross-env TAG=dev TARGET=msedge-mv3 pnpm run pack-signed",
    "release-all-prod": "pnpm run release-chrome-prod && pnpm run release-msedge-prod",
    "release-all-dev": "pnpm run release-chrome-dev && pnpm run release-msedge-dev",
    "release-all": "pnpm run release-all-prod && pnpm run release-all-dev && pnpm run refreshdeploy"
  }

FYI, pack-signed script will create a CRX file with a pem file and refreshDeploy will generate a "dist" folder with all crx, zip files and update.xml files (extensions are not published trough the official stores).

Is there any way to simplify this setup ?

Thanks for your feedback

[louisgv]

Feel like this is something that #162 should handle - basically you can specify a list of target and tag and it will sequentially build each target.

In term of simplifying your current setup, seems like it should be simple for you to make a scripts/build-all.ts that basically run all of your release channel sequentially? (I don't think you should run them in parallel bc each build will consume all worker threads available within nodejs runtime).

[stevebeauge]

Sure the #162 is promising, but I don't expect it to be released soon (the issue is 1yr old and currently all the logic seems to be inside the CLI). I'll keep an eye on it, but I'll have to live without by now.

Regarding the simplification you suggest, it may help. Let's close the issue for now