How to combine multiple env variables in package.json's manifest ?

[stevebeauge]

Because we are hosting internally our extension, we have to provide the update_url field of the manifest.

We have a matrix of tags (dev or prod) and browsers (msedge or chrome). Please note that by "dev" we mean a beta version, for testing.

Each of the combination will ends in a specific url that must match this form:

https://browserext-dev.ourcompany.com/dev/ourextension-msedge-mv3-dev.update.xml
https://browserext.ourcompany.com/prod/ourextension-msedge-mv3-prod.update.xml
https://browserext-<<dev or nothing>>.ourcompany.com/<<tag>>/ourextension-<<browser>>-mv3-<<tag>>.update.xml
....

We build each variation using --target=msedge-mv3 --tag=prod (for example) switches

I have trouble generating this URL in the manifest.

What I tried first:

1. play with env files:
   we previously had .env.dev and .env.prod files which is working to fix some settings like the app id and extension name. I tried to create .env.tag.browser or .env.browser.tag (.env.msedge.prod or .env.prod.msedge) files which contains a PLASMO_PUBLIC_UPDATE_URL variable. However, it seems that these env files are ignored.

2. compose the update_url using multiple environment variables.
   I tried to define the update URL like this (PLASMO_PUBLIC_HOSTING_ROOT env is defined in the .env.tag files):

   "update_url": "$PLASMO_PUBLIC_HOSTING_ROOT/$PLASMO_TAG/ourextension-$PLASMO_BROWSER-mv3-$PLASMO_TAG.update.xml"
   

However, only the first variable is populated. The actual value in the generated manifest is

  "update_url": "https://browserext-dev.ourcompany.com/$PLASMO_TAG/ourextension-$PLASMO_BROWSER-mv3-$PLASMO_TAG.update.xml"

What can I do?

There's still no plasmo api that we can use to hook the build process to perform custom operation.

[stevebeauge]

Just found that I can use in my package.json build script :

"build" : "cross-env PLASMO_TAG=prod PLASMO_BROWSER=msedge plasmo build --target=msedge-mv3 --tag=prod 

This way, the env variables are injected properly in the manifest.

It seems that plasmo is not providing this variables in the manifest builder.