How can I tell if the FireFox extensions I use are WebExtensions or not?
I've recently read an article on Mozilla's blog about how support for "legacy" extensions will soon be phased out in favor of WebExtensions.
How can I tell whether the extensions I have installed are WebExtensions or "legacy" extensions (as defined by the aforementioned blog post)?
https://addons.mozilla.org/ doesn't seem to show this information.
I know I can browse to my FireFox profile on Windows by going to %AppData%MozillaFirefoxProfiles and in my <profile>extensions folder I have some .xpi files which are just zip files. But, if I open them, what should I look for inside in order to determine whether they are WebExtensions or not?
I'm mainly interested in knowing which extensions I have that I could potentially lose if the developers don't update/rewrite them as WebExtensions. If there is an easier way than the idea I had of checking in the extensions folder, please let me know.
firefox firefox-extensions
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
add a comment |
I've recently read an article on Mozilla's blog about how support for "legacy" extensions will soon be phased out in favor of WebExtensions.
How can I tell whether the extensions I have installed are WebExtensions or "legacy" extensions (as defined by the aforementioned blog post)?
https://addons.mozilla.org/ doesn't seem to show this information.
I know I can browse to my FireFox profile on Windows by going to %AppData%MozillaFirefoxProfiles and in my <profile>extensions folder I have some .xpi files which are just zip files. But, if I open them, what should I look for inside in order to determine whether they are WebExtensions or not?
I'm mainly interested in knowing which extensions I have that I could potentially lose if the developers don't update/rewrite them as WebExtensions. If there is an easier way than the idea I had of checking in the extensions folder, please let me know.
firefox firefox-extensions
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
add a comment |
I've recently read an article on Mozilla's blog about how support for "legacy" extensions will soon be phased out in favor of WebExtensions.
How can I tell whether the extensions I have installed are WebExtensions or "legacy" extensions (as defined by the aforementioned blog post)?
https://addons.mozilla.org/ doesn't seem to show this information.
I know I can browse to my FireFox profile on Windows by going to %AppData%MozillaFirefoxProfiles and in my <profile>extensions folder I have some .xpi files which are just zip files. But, if I open them, what should I look for inside in order to determine whether they are WebExtensions or not?
I'm mainly interested in knowing which extensions I have that I could potentially lose if the developers don't update/rewrite them as WebExtensions. If there is an easier way than the idea I had of checking in the extensions folder, please let me know.
firefox firefox-extensions
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
I've recently read an article on Mozilla's blog about how support for "legacy" extensions will soon be phased out in favor of WebExtensions.
How can I tell whether the extensions I have installed are WebExtensions or "legacy" extensions (as defined by the aforementioned blog post)?
https://addons.mozilla.org/ doesn't seem to show this information.
I know I can browse to my FireFox profile on Windows by going to %AppData%MozillaFirefoxProfiles and in my <profile>extensions folder I have some .xpi files which are just zip files. But, if I open them, what should I look for inside in order to determine whether they are WebExtensions or not?
I'm mainly interested in knowing which extensions I have that I could potentially lose if the developers don't update/rewrite them as WebExtensions. If there is an easier way than the idea I had of checking in the extensions folder, please let me know.
firefox firefox-extensions
firefox firefox-extensions
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
asked Feb 19 '17 at 6:50
Keith HallKeith Hall
301110
301110
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
If there is a manifest.json file in the root of the xpi file, then it is a WebExtension. https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
Every WebExtension must contain a file called "manifest.json".
If there is a package.json file in the root of the xpi file, then it is a legacy add-on. https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Getting_Started_(jpm)
The
package.jsonfile contains manifest data for your add-on, providing not only descriptive information about the add-on for presentation in the Add-ons Manager, but other metadata required of add-ons.
We are planning to deprecate the use by Firefox add-ons of the techniques described in this document.
Don't use these techniques to develop new add-ons. Use WebExtensions instead.
(Discovered the latter page by viewing the history of the Add-ons page, until I found a revision which contained a link to the old way of building addons (https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons$revision/1144290))
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
It would be good an alternative to identify XUL/webextension addons from the browser UI. Looking manually into each xpi file is no user friendly.
– Daniel Perez
Jan 21 at 16:31
add a comment |
I found an alternative to identify webextensions from a webbrowser.
- Install crxviewer webextension
- Go to addons, CRX viewer
- Click on "Open viewer" on the bottom of addon page
- Click on "Browse" button
- Navigate to your extensions folder
- Select a .xpi file and click "Open" button
On the left side you can find those files that can identify XUL/webextension:
- /manifest.json or /webextension/manifest.json (for Webextension)
+ - /package.json (for Webextension) (some XUL extensions have this file also)
optionally:
- /chrome.manifest (most XUL extension have this file)
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1180416%2fhow-can-i-tell-if-the-firefox-extensions-i-use-are-webextensions-or-not%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If there is a manifest.json file in the root of the xpi file, then it is a WebExtension. https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
Every WebExtension must contain a file called "manifest.json".
If there is a package.json file in the root of the xpi file, then it is a legacy add-on. https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Getting_Started_(jpm)
The
package.jsonfile contains manifest data for your add-on, providing not only descriptive information about the add-on for presentation in the Add-ons Manager, but other metadata required of add-ons.
We are planning to deprecate the use by Firefox add-ons of the techniques described in this document.
Don't use these techniques to develop new add-ons. Use WebExtensions instead.
(Discovered the latter page by viewing the history of the Add-ons page, until I found a revision which contained a link to the old way of building addons (https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons$revision/1144290))
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
It would be good an alternative to identify XUL/webextension addons from the browser UI. Looking manually into each xpi file is no user friendly.
– Daniel Perez
Jan 21 at 16:31
add a comment |
If there is a manifest.json file in the root of the xpi file, then it is a WebExtension. https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
Every WebExtension must contain a file called "manifest.json".
If there is a package.json file in the root of the xpi file, then it is a legacy add-on. https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Getting_Started_(jpm)
The
package.jsonfile contains manifest data for your add-on, providing not only descriptive information about the add-on for presentation in the Add-ons Manager, but other metadata required of add-ons.
We are planning to deprecate the use by Firefox add-ons of the techniques described in this document.
Don't use these techniques to develop new add-ons. Use WebExtensions instead.
(Discovered the latter page by viewing the history of the Add-ons page, until I found a revision which contained a link to the old way of building addons (https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons$revision/1144290))
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
It would be good an alternative to identify XUL/webextension addons from the browser UI. Looking manually into each xpi file is no user friendly.
– Daniel Perez
Jan 21 at 16:31
add a comment |
If there is a manifest.json file in the root of the xpi file, then it is a WebExtension. https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
Every WebExtension must contain a file called "manifest.json".
If there is a package.json file in the root of the xpi file, then it is a legacy add-on. https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Getting_Started_(jpm)
The
package.jsonfile contains manifest data for your add-on, providing not only descriptive information about the add-on for presentation in the Add-ons Manager, but other metadata required of add-ons.
We are planning to deprecate the use by Firefox add-ons of the techniques described in this document.
Don't use these techniques to develop new add-ons. Use WebExtensions instead.
(Discovered the latter page by viewing the history of the Add-ons page, until I found a revision which contained a link to the old way of building addons (https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons$revision/1144290))
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
If there is a manifest.json file in the root of the xpi file, then it is a WebExtension. https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
Every WebExtension must contain a file called "manifest.json".
If there is a package.json file in the root of the xpi file, then it is a legacy add-on. https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Getting_Started_(jpm)
The
package.jsonfile contains manifest data for your add-on, providing not only descriptive information about the add-on for presentation in the Add-ons Manager, but other metadata required of add-ons.
We are planning to deprecate the use by Firefox add-ons of the techniques described in this document.
Don't use these techniques to develop new add-ons. Use WebExtensions instead.
(Discovered the latter page by viewing the history of the Add-ons page, until I found a revision which contained a link to the old way of building addons (https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons$revision/1144290))
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
edited Feb 19 '17 at 10:17
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
answered Feb 19 '17 at 9:35
Keith HallKeith Hall
301110
301110
It would be good an alternative to identify XUL/webextension addons from the browser UI. Looking manually into each xpi file is no user friendly.
– Daniel Perez
Jan 21 at 16:31
add a comment |
It would be good an alternative to identify XUL/webextension addons from the browser UI. Looking manually into each xpi file is no user friendly.
– Daniel Perez
Jan 21 at 16:31
It would be good an alternative to identify XUL/webextension addons from the browser UI. Looking manually into each xpi file is no user friendly.
– Daniel Perez
Jan 21 at 16:31
It would be good an alternative to identify XUL/webextension addons from the browser UI. Looking manually into each xpi file is no user friendly.
– Daniel Perez
Jan 21 at 16:31
add a comment |
I found an alternative to identify webextensions from a webbrowser.
- Install crxviewer webextension
- Go to addons, CRX viewer
- Click on "Open viewer" on the bottom of addon page
- Click on "Browse" button
- Navigate to your extensions folder
- Select a .xpi file and click "Open" button
On the left side you can find those files that can identify XUL/webextension:
- /manifest.json or /webextension/manifest.json (for Webextension)
+ - /package.json (for Webextension) (some XUL extensions have this file also)
optionally:
- /chrome.manifest (most XUL extension have this file)
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
add a comment |
I found an alternative to identify webextensions from a webbrowser.
- Install crxviewer webextension
- Go to addons, CRX viewer
- Click on "Open viewer" on the bottom of addon page
- Click on "Browse" button
- Navigate to your extensions folder
- Select a .xpi file and click "Open" button
On the left side you can find those files that can identify XUL/webextension:
- /manifest.json or /webextension/manifest.json (for Webextension)
+ - /package.json (for Webextension) (some XUL extensions have this file also)
optionally:
- /chrome.manifest (most XUL extension have this file)
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
add a comment |
I found an alternative to identify webextensions from a webbrowser.
- Install crxviewer webextension
- Go to addons, CRX viewer
- Click on "Open viewer" on the bottom of addon page
- Click on "Browse" button
- Navigate to your extensions folder
- Select a .xpi file and click "Open" button
On the left side you can find those files that can identify XUL/webextension:
- /manifest.json or /webextension/manifest.json (for Webextension)
+ - /package.json (for Webextension) (some XUL extensions have this file also)
optionally:
- /chrome.manifest (most XUL extension have this file)
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
I found an alternative to identify webextensions from a webbrowser.
- Install crxviewer webextension
- Go to addons, CRX viewer
- Click on "Open viewer" on the bottom of addon page
- Click on "Browse" button
- Navigate to your extensions folder
- Select a .xpi file and click "Open" button
On the left side you can find those files that can identify XUL/webextension:
- /manifest.json or /webextension/manifest.json (for Webextension)
+ - /package.json (for Webextension) (some XUL extensions have this file also)
optionally:
- /chrome.manifest (most XUL extension have this file)
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
answered Jan 21 at 17:30
Daniel PerezDaniel Perez
688
688
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1180416%2fhow-can-i-tell-if-the-firefox-extensions-i-use-are-webextensions-or-not%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
