manifest.json as Object to test extensions with GitHub Actions.

[xtc44 xtc44]

Hello,

Is there a Chromium Command Line Switch combo available already?

I have searched for "manifest.json" in the "Conversations"

and found nothing suitable.

Could somebody open an issue for Chromium?

Implement a "--use-object-as-manifest=${myManifestDictionary}"

for testing.

Playwright may use it as argument for

chromium.launchPersistentContext().

It must override `--load-extension=${pathToExtension}`

load manifest.json from file part.

Expected result:

Dev can test various configurations without touching manifest.json

file.

Additional context:

Check available Playwright Browser brands after git push

with GitHub Actions workflow.

Which is impossible with one static manifest.json

(v2 or v3, or FireFox, ...), nailed to the repository.

Dev copies content of manifest.json into the test module

"const myConfig={"version": "1.0.0", ...}".

Add/Remove/Override manifest keys.

Thank you for your effort.

Regards

[Oliver Dunk]

Hi,

We don't currently support a command line switch like this and I expect we would be unlikely to support it in the future. We are trying to reduce the number of command line flags that can load extensions as these have unfortunately been used for abuse, including loading unwanted extensions on users machines.

Could you continue to load your extension from a directory but update the manifest from your own code? You could create a new directory with the correct files and then call launchPersistentContext afterwards.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/ce0230e2-8365-4b3d-ae2b-ca86816508b9n%40chromium.org.