3 ms·
I usually keep a common source folder for all browsers. This includes a common manifest (V2, still experimenting with V3). At build time a script generates a br
by isodev 5y ago
I usually keep a common source folder for all browsers. This includes a common manifest (V2, still experimenting with V3). At build time a script generates a browser specific flavour of the manifest and copies all resources into a target folder (e.g /dist-chrome, /dist-safari, /dist-firefox) to create a bundle per browser and apply browser specific tweaks (like copying resources into an Xcode project for Safari etc).
- falafelite 5y agoInteresting! I’ve got something like that (doesn’t work properly for Chrome yet) going; if it is open source on git somewhere, I’d love to see it. If not, no worries!
- dewey 5y agoHow do you develop it (having the extension enabled in the browser) with this strategy? Are you just continuously re-building on changes and the browser picks it up?