Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install self-hosted chrome extension to chrome #111

Open
mtami-zoor opened this issue Jan 13, 2024 · 1 comment
Open

install self-hosted chrome extension to chrome #111

mtami-zoor opened this issue Jan 13, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@mtami-zoor
Copy link

I've built a custom Chrome extension, packed it into a CRX file, and got the extension ID.
Also, I have self-hosted and I can manually check it's accessible.

When creating a chrome browser via API, I can inspect the policy.json inside the container which has the [id;self-hosted URL] in ExtensionInstallForcelist and the id listed in ExtensionInstallAllowlist, However, I can't see the chrome extension installed when login to the neko room.

Has anyone tried this before and faced a similar issue?

@m1k1o
Copy link
Owner

m1k1o commented Jan 14, 2024

I never tried installing from other than official URL.

Google chrome supports --load-extension=/path/to/unpacked/extension argument, though it cannot be set from API yet.

@m1k1o m1k1o added the enhancement New feature or request label Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants