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
It would be good to explore what the modern options for Chrome Extension boilerplates / frameworks / bundlers / supporting tooling are; ideally something that supports TypeScript, and probably that uses Vite or similar. Being able to automatically build/bundle/deploy updates from GitHub actions would be useful too.
Resources
A few non-exhaustive resources that may be worth looking into deeper.
Building my first browser extension: should I use a framework?
⚠️ Spoiler ⚠️
We decided to use a framework!
We chose Plasmo because the other options available were not suitable for us:
— CRXJS: Chrome specific, we had the ambition to deploy to other browsers in the future;
— Bedframe: early access only.
Choosing the Right Framework for Your Chrome Extension: A Comprehensive Guide
In the ever-evolving landscape of web development, selecting the right framework for building Chrome extensions is a crucial decision. Each framework brings its own set of features and advantages to the table. In this article, we’ll explore three powerful tools, such as Parcel.js, Plasmo, and Vite, to help you make an informed choice for your next Chrome extension project.
WXT does not currently support automated publishing for Safari. Safari extensions require a native MacOS or iOS app wrapper, which WXT does not create yet. For now, if you want to publish to Safari, follow this guide:
WXT
Next-gen framework for developing web extensions.
It's like Nuxt, but for Chrome Extensions
MV2 and MV3
Build Manifest V2 or V3 extensions for any browser using the same codebase.
File Based Entrypoints
Manifest is generated based on files in the project with inline configuration.
TypeScript
Create large projects with confidence using TS by default.
Automated Publishing
Automatically zip, upload, submit, and publish extensions.
Frontend Framework Agnostic
Works with any front-end framework with a Vite plugin.
Bootstrap a New Project
Get started quickly with several awesome project templates.
Bundle Analysis
Tools for analyzing the final extension bundle and minimizing your extension's size.
WXT's simplifies the chrome extension development process by providing tools for zipping and publishing, the best-in-class dev mode, an opinionated project structure, and more. Iterate faster, develop features not build scripts, and use everything the JS ecosystem has to offer.
Browser Platform Publisher
A GitHub action from Plasmo to publish your browser extension to every web store/add-ons marketplace. This action and its dependencies are open-sourced under the MIT license.
Browser Market Submit
A NodeJS library from Plasmo to submit browser extensions to multiple stores. It is made to be used in the Browser Platform Publisher action.
Parcel combines a great out-of-the-box development experience with a scalable architecture that can take your project from just getting started to massive production application.
It would be good to explore what the modern options for Chrome Extension boilerplates / frameworks / bundlers / supporting tooling are; ideally something that supports TypeScript, and probably that uses Vite or similar. Being able to automatically build/bundle/deploy updates from GitHub actions would be useful too.
Resources
A few non-exhaustive resources that may be worth looking into deeper.
Lists / Blogs / etc
Extension Frameworks
Extension Store Submission
Boilerplates
Bundlers (non browser extension specific)
Etc
See Also
The text was updated successfully, but these errors were encountered: