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

Migrate to manifest V3 for Chrome, update tech stack, major refactoring #40

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

alvkn
Copy link

@alvkn alvkn commented Nov 19, 2024

As I've noted here, Firefox barely supports manifest v3 (there are some issues with service workers), and there are many ways to handle the separation of manifests for different browsers - and this is one of them.

What was done:
I did a major refactoring, removed obsolete (in my opinion) libs like browserify and others.

Vite is chosen as the bundler to provide an easy and robust way to build the extension without having to manually copy files (except the license file).

Mocha is replaced by Vitest to eliminate the need to compile TypeScript-based tests before running - API is almost the same

vite-plugin-web-extension plugin is used to handle different manifest versions in the most optimal way (in my opinion).

Also, updated the code to use modern JS approaches (const and let instead of var), applied code formatting, unified indent size across the codebase.

Fixes #34

@ForNeVeR ForNeVeR self-assigned this Nov 19, 2024
@ForNeVeR ForNeVeR self-requested a review November 19, 2024 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate to plugin manifest v3
2 participants