Chrome Extension V3 Boilerplate

Chrome Extension, TypeScript and Visual Studio Code

Built With

In addition we use:

Tailwind Prettier Plugin The Tailwind Prettier Plugin automatically sorts tailwind classes. No need to use a VS Code Extension for that purpose anymore.
MV3 Hot Reload MV3 Hot Reload watches file changes and sends a reload message to your extension under development in case of a file change.
Husky Husky offers an elegant way to manage git hooks.
Commitlint Commitlint enforces commit messages to follow a certain format. You can find the rules in commitlint.config.js.
Dot Env Webpack Dot Env Webpack gives the ability to access environment variables defined in your .env, .env.development etc. via 'process.env'. from files within your web application.

yarn yarn run prepare yarn run dev:scripts

src/background Files for the background service worker
src/content Files for the contect script which has access to the page's DOM.
src/options Files for the options page.
src/popup Files for the popup widget which appear when the user clicks on the extension icon in the browser bar.
dist/manifest.json Config/Manifest file of the extension (permissions, icons, etc.)
dist/images Folder for images and icons used in the extension.

After you have setup the project you only need to run yarn run dev:scripts to keep working on your extension.

Simply run yarn run build to obtain an optimized production build. Afterwards, zip the dist folder and upload it to the Chrome Extension Store.

A commit message has the following format: <type>: message.
Possible types:

feat
fix
docs
chore
style
refactor
ci
test
perf
revert

Example: chore: update eslint package