You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we try to download the extension, we use it's Chrome Store id.
But when accessing the extracted extension, the inner id is different.
Currently, we use EXTENSION_CHROME_INNER_IDS. But it also means that if we download the new verions of the extension, the inner id is different.
To get the inner id we now manually go to the Chrome extension tab inside the Playwright and update the IDs.
We need to parse the CRX header to programmatically derive the true extension ID. That’s how Chrome figures out the hashed ID we see in chrome://extensions. Once we do that, we won’t need to hardcode or guess the “inner extension ID” in our config.
We write our own solution of getExtensionIdFromCrx if it is simple.
We rely on the third-party solution, some sort of crx related npm library
less desired We write a Playwright test that manually goes to the chrome extensions and grabs the extension id
The text was updated successfully, but these errors were encountered:
When we try to download the extension, we use it's Chrome Store
id
.But when accessing the extracted extension, the
inner id
is different.Currently, we use
EXTENSION_CHROME_INNER_IDS
. But it also means that if we download the new verions of the extension, theinner id
is different.To get the
inner id
we now manually go to the Chrome extension tab inside thePlaywright
and update the IDs.We need to parse the CRX header to programmatically derive the true extension ID. That’s how Chrome figures out the hashed ID we see in
chrome://extensions
. Once we do that, we won’t need to hardcode or guess the “inner extension ID” in our config.getExtensionIdFromCrx
if it is simple.crx
relatednpm
libraryThe text was updated successfully, but these errors were encountered: