←back to thread

381 points cezaraugustodev | 2 comments | | HN request time: 0.541s | source

Hello HN! I'm the creator and solo developer of Extension.js, a development tool for browser extensions with built-in support for TypeScript, WebAssembly, React, and modern JavaScript. Developers use it to spend less time configuring the compilation config or learning new frameworks and more time actually writing code.

Most projects similar to Extension.js rely on some sort of abstraction or configuration to get started, making the initial development process slow given the extra learning curve and setup guidelines. By using Extension.js, adding the package to your npm scripts is all it takes to get started developing cross-browser extensions with no build configuration. Say goodbye to extensive configurations to create your next cross-browser extension!

Creating a new extension is super easy. This command will create a new extension named "my-extension" in the current working directory. In your terminal:

npx extension@latest create my-extension

You can also create an extension based on any extension hosted on GitHub. Just add the URL of the folder where the manifest is located and run `npx extension@latest dev <github_url>`. For instance, you can try the Chrome Sample "page-redder" (https://github.com/GoogleChrome/chrome-extensions-samples/tr...).

I first created this project as a way to teach others how to develop browser extensions, until I realized that a good amount of my teachings would involve setting up a new project. With Extension.js, the abstractions and configurations needed to create cross-browser extensions are handled by a simple command-line interface, allowing developers to focus on the actual development of their next extension.

Any feedback is appreciated. I've been using it for a while in personal projects but it is now mature enough for others to give it a go. I'm looking forward to hear what you all have to say! :D

Show context
kosolam ◴[] No.40221187[source]
Need to change the title it’s browser extensions not Web extensions.
replies(1): >>40224865 #
sureIy ◴[] No.40224865[source]
That’s wrong: https://github.com/w3c/webextensions
replies(1): >>40234039 #
kosolam ◴[] No.40234039[source]
Please read these quotes from these links to better understand why it’s not wrong.

“Extension is a plug-and-play, zero-config, cross-browser extension development tool for browser extensions with built-in support for TypeScript, WebAssembly, React, and modern JavaScript.”

“WebExtensions are a way to write browser extensions: that is, programs installed inside a web browser that modify the behavior of the browser or web pages loaded by the browser. WebExtensions are built on a set of cross-browser APIs, so WebExtensions written for Google Chrome, Opera, or Edge will, in most cases, run in Firefox too.”

replies(1): >>40258639 #
sureIy ◴[] No.40258639[source]
You’re making up differentiation where there is none. Browser extensions are called WebExtensions. The terms are used interchangeably in practice.

> WebExtensions are a way to write browser extensions

Even if “technically correct”, the tool still specifically creates WebExtensions, it does not create “non-WebExtension browser extensions”

replies(1): >>40263639 #
1. kosolam ◴[] No.40263639[source]
You are welcome to go to their respective repos and make your arguments there. I just pasted the quotes here.
replies(1): >>40264786 #
2. sureIy ◴[] No.40264786[source]
They’re right, it’s your “correcting” comment that’s wrong