(2 comments) (0 reactions) (0 assignees)JavaScript (44,030 stars) (2,274 forks)batch import

Good First Issue

Description

🙋 feature request

Chrome supports two keys to specify the options page:

options_ui
options_page

MDN reports that options_page is deprecated and so does Parcel's schema:

https://github.com/parcel-bundler/parcel/blob/53633df12ad9bba5d6ed5360e935fde8de0342fe/packages/transformers/webextension/src/schema.js#L289

However that doesn't reflect reality, Chrome does not deem the key deprecated in their docs and even Firefox eventually added support for it: https://bugzilla.mozilla.org/show_bug.cgi?id=1816960

You can find further reasoning in the bugzilla.

🤔 Expected Behavior

options_page should be equivalent to options_ui.page

😯 Current Behavior

The key is ignored and the specified options.html is not processed.

💻 manifest.json demo

{
	"$schema": "https://json.schemastore.org/chrome-manifest",
	"name": "options_page minimal extension",
	"version": "0.0.0",
	"manifest_version": 3,
	"options_page": "options.html"
}

Contributor guide

Tech stack: javascript
Domain: build system
Issue type: feature
Difficulty: 2
Estimated time: 1-3 hours
Activity status: fresh
Clarity: clear
Prerequisites: Web extensions manifestParcel transformer internals
Newbie friendliness: 75
Research direction: Start by examining the schema file at `packages/transformers/webextension/src/schema.js`, particularly the handling of `options ui`. The fix should alias `options page` to `options ui.page` in the transformer's manifest validation and processing logic. Check existing tests and add a test case for the `options page` key. Look for any references to `options page` in the codebase to ensure consistent handling.