-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Are there extensions in the web store that were created using this repo? #128
Comments
There are examples of browser extensions in the repositoryBlazor.BrowserExtension.Samples. You can also look at a list of GitHub projects dependent on this package in the dependents insight page. EdgeExtensionsBlazor is published on the Edge extension store. Amazing-Favorites/Amazing-Favorites is published on the Edge and Chrome extension store. |
Amazing favorites is using manifest version 2 which is getting deprecated these days. Is there an extension in Chrome Store that uses version 3? My concern is that Google might not accept extensions developed with Blazor or WebAssembly in manifest 3 as they have more stringent rules with it. I noticed in the extension files with *.dll.br extension. Are these the actual dll's? I am not sure what the .br extension is about. Doesn't Google check the regular Javascript based extensions for security holes and malware? I am not sure how they do the same for webassembly files. |
.Net 7 and before compiles to
Chrome extensions have a sample project for showcasing using wasm in extension, which would not make sense if they don't allow extensions built with wasm to be published. |
Are there extensions in the web store that were created using this repo?
Are there working examples of browser extensions on Github that are based on this repo?
The text was updated successfully, but these errors were encountered: