Addon test not ready to run with JPM



Add-on SDK
2 years ago
5 months ago


(Reporter: Jacobo Aragunde Pérez, Unassigned)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



2 years ago
User Agent: Mozilla/5.0 (Fedora; Linux x86_64) AppleWebKit/601.1 (KHTML, like Gecko) Version/8.0 Safari/601.1 Epiphany/3.16.3

Steps to reproduce:

Ran tests with gulp test:addons

Actual results:

Several warnings and one error appear when running the page-worker addon:

JPM [warning] Either a `title` or `name` property should be specified in `package.json`
as the addon's displayable name on AMO.

JPM [warning] The `name` field in `package.json` should contain only lowercase
alphanumeric characters, underscore, dot, or dashes, and cannot
start with an underscore or dash, to be compatible with npm
naming conventions.

JPM [warning] The `version` entry must be specified, and it should follow semantic
versioning rules. For example, it must be a string containing three
values indicating major, minor, and patch versions. For example:


JPM [error] Error: A valid identification must be defined in `package.json` to be
able to be installed by Firefox. Adding a `name` field to the
`package.json` works as identification, or an `id` property that
is formatted as a GUID or address, like:


IF MOVING FROM CFX: The cfx tool adds `@jetpack` to your `id` field
if invalid -- to transition to jpm, adding `@jetpack` will fix the issue,
and also retain the same ID used on AMO.

Comment 1

2 years ago
When I addressed the error and warnings mentioned above, I got this other error:

JPM [error] Error: The addon has no valid entry point. Either create an entry point
at `./index.js`, or set the `main` property to a valid path in
your addon.

Comment 2

2 years ago
Created attachment 8680598 [details] [review]
Pull request

Comment 3

2 years ago
Any chance to get the patch reviewed? If necessary, I can submit it through other means. Thanks in advance!
Last Resolved: 5 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.