Extensions are disabled when running Chrome in Sharedown

[mikhail-ict]

When the only way to login is having the following Chrome extension installed: https://chrome.google.com/webstore/detail/windows-accounts/ppnbnpeolgkicgegkbkbjmhlideopiji

Since Sharedown launches Chrome (Built-in or external) with no extensions enabled – how to have it run with that specific extension being on?

Thank you.

[kylon]

this is tricky according to docs you can load unpacked extensions so using this to get the crx or chrome itself, i think, and unpack it (it is a zip file)

then doing this in preload.js

[mikhail-ict]

I actually tried doing this through GUI in Chrome by turning on the Dev mode in Extensions and then pointing to the unpacked location of the extension, but it did not work for me...

I have the Windows version installed with sharedown.Setup.5.3.2.exe... I can't find preload.js file anywhere.

I even tried putting in flags in Custom Chrome/Chromium executable field, but this is not an option, of course... Can the flags be changed at the Settings level in future?

Thank you.

[kylon]

the method above is for source, download the repo, apply the edit and paste the extension folder in sharedown repo folder and run with npm start

[mikhail-ict]

Thank you so much for the instructions. It worked – the extension was there when Chrome was loaded.

But I got this message when signing in:

The Chrome extension is not supported on your version of Windows. You must be on Windows 10 version 1703 and above. Alternatively, you can use Microsoft Edge or Internet Explorer to access this application.

Though the same browser works perfectly with that extension when not being called from Sharedown. So there might be some awareness that the extension is being loaded unpacked on the sign-in end?

[mikhail-ict]

I loaded the unpacked extension in the normal circumstances and it gave me the same error. Though the original .crx-installed version is working as intended.

Can it be loaded directly from Chrome Web Store?

If the extension is hosted on the Chrome Web Store, you might use the --enable-easy-off-store-extension-install and --force-install-webstore-item=<extension_id> command-line switches along with the extension’s update URL.

[kylon]

If the extension is hosted on the Chrome Web Store, you might use the --enable-easy-off-store-extension-install and --force-install-webstore-item=<extension_id> command-line switches along with the extension’s update URL.

afaik not supported, install is not working too it is possible puppeteer has a default arg that must be removed for this to work