Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cezaraugustodev
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
cezaraugustodev
2y ago
Safari and Firefox are next, feel free to subscribe to the issues below so you know when Extension.js supports them. - Safari https://github.com/cezaraugusto/extension.js/issues/46 - Firefox https:/
2.
▲
by
cezaraugustodev
2y ago
In your case, Extension.js can help by managing the configuration details that are usually overlooked in general web development. After copying a few files from the Chrome extension documentation site, you'll need to manually enable &q
3.
▲
by
cezaraugustodev
2y ago
FYI There is a new issue to track progress and enable Safari support https://github.com/cezaraugusto/extension.js/issues/46
4.
▲
by
cezaraugustodev
2y ago
Thanks for that!
5.
▲
by
cezaraugustodev
2y ago
That's great! I'm glad you will give it a try
6.
▲
by
cezaraugustodev
2y ago
That's interesting, what do you mean? An abstraction for the manifest apply dev defaults or instructions on how each major part should work?
7.
▲
by
cezaraugustodev
2y ago
Thank you! The ecosystem for developing extensions could be so much better, hope we can help with that
8.
▲
by
cezaraugustodev
2y ago
Haha, thanks! It’s not in the immediate plans, but meanwhile, I'm sure there are some good libraries on npm for that :)
9.
▲
by
cezaraugustodev
2y ago
I'm glad to hear!
10.
▲
by
cezaraugustodev
2y ago
Totally relate. Extension development should be fun, right? Hope Extension.js can help you with your next project!
11.
▲
by
cezaraugustodev
2y ago
Extension.js can help you creating a new extension using React in no time: npx extension create my-react-extension --template=react But I guess it doesn't make it any easier to modify the behavior of fancy modern web sites :_(
12.
▲
by
cezaraugustodev
2y ago
Great question! The biggest difference, in my opinion, is that Plasmo is a framework, which means you have to learn its abstractions and rely on specific samples tailored for these abstractions to create new extensions. There are config fil
13.
▲
by
cezaraugustodev
2y ago
Yes, the manifest.json is a required file for all extensions, and the package.json file provides necessary package metadata. web-ext is excellent, but it seems there are no plans for the project to support more browsers than it currently do
14.
▲
by
cezaraugustodev
2y ago
The plugin for Firefox is on the way, but any community support is highly appreciated.
15.
▲
by
cezaraugustodev
2y ago
Thanks! Firefox support will come in the next update. Stay tuned! :)
16.
▲
by
cezaraugustodev
2y ago
Haha glad to hear that
17.
▲
by
cezaraugustodev
2y ago
No worries :) but Chrome and Edge are indeed different browsers. Support for Firefox and Safari is next.
18.
▲
by
cezaraugustodev
2y ago
That's great feedback, thank you. Will consider the removal.
19.
▲
by
cezaraugustodev
2y ago
Sure thing! There will be support for Firefox very soon
20.
▲
by
cezaraugustodev
2y ago
HN has a character limitation for the post title and changing the word made the title fit just fine :)
21.
▲
by
cezaraugustodev
2y ago
Thank you! I'm glad you liked the readme as well :D
22.
▲
by
cezaraugustodev
2y ago
Thanks for the kind words!
23.
▲
by
cezaraugustodev
2y ago
Thanks! I do plan to support all major browsers in the near future, including Safari :)
24.
▲
by
cezaraugustodev
2y ago
Thanks a lot! You can run your Mozilla Add-On on Chrome or Edge by adding a --polyfill flag, but for now you need to manually add the extension to Firefox. I do plan to support Firefox in the near future, but no browser runner available at
25.
▲
Show HN: I made a CLI tool to create web extensions with no build configuration
(github.com)
381 points
by
cezaraugustodev
2y ago
|
87 comments
26.
▲
npx extension create my-extension – zero-config web extension development tool
(github.com)
1 points
by
cezaraugustodev
2y ago
|
0 comments