-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add file extension option to web-ext build
#393
Comments
What about an manifest value which allows to save this setting persistent and also allows to save the build multiple times with different file extensions? Could be a step for Firefox&Chrome packaging at once? I'm not sure if the often discussed mozilla.json file is already a reality, but I guess there could be a place for something like this. |
Could you explain this further? Can't you just use a
I think a good solution here would be to implement support for a web-ext config file that you could commit to your repo to set defaults: #176 |
Also, there isn't a |
When I didn't get it wrong it is not possible to install a .zip bundled add-on permanently in a (non-stable) Firefox build, is it? I'm doing this for longer testings of my (.xpi) add-ons.
That sounds very good :) |
You can install a |
I'm sorry. I forgot the most important information. Is it also possible to install a .zip addon permanently when it's not signed? I might remembering reading something like .zip are good for temporary testing or something. Unfortunately, my GitHub feed is spamming a huge information flow, so that I mostly just skim the issues, prs.. |
I think so. Just like with XPIs, you would need to either use a pre-production or unbranded build with signing disabled. |
Add an option to build a package file with something other than the
.xpi
extensionThe text was updated successfully, but these errors were encountered: