Closed pdehaan closed 6 years ago
We can also use the same JPM --addon-dir
flag to specify the addon directory during jpm run
, which would save us a cd addon &&
.
"addon": "jpm run --addon-dir addon -b nightly --prefs .jpm-prefs.json --profile ./Profile --no-copy --binary-args -jsconsole",
Although we'd still need to either do the mkdir -p ./Profile &&
to pre-create that directory [every time somebody runs npm run addon
], or else just commit an empty Profile directory into the repo and add a nested .gitignore file in it, to save constantly doing a mkdir -p
on a potentially already existing directory.
Running
npm run build
will now generate a file in the root directory named "tab-split-0.1.0.xpi" (so we'd want to add*.xpi
to the .gitignore file probably.Not sure why the file is being
null.xpi
. Maybe we need an "addon/manifest.json" file with values copied from package.json. Currently runningnpx addons-linter tab-split-0.1.0.xpi
returns the following: