1305527 - publish new version of eslint-plugin-mozilla to npm

Status: RESOLVED FIXED

(Developer Infrastructure :: Lint and Formatting, defect)

Description

[Peter deHaan [:pdehaan]]

https://www.npmjs.com/package/eslint-plugin-mozilla says "0.0.3 is the latest release"

But the npm page is virtually blank, apart from a broken link to mozilla-central.

https://dxr.mozilla.org/mozilla-central/source/tools/lint/eslint/eslint-plugin-mozilla/package.json says the latest version is "0.2.1".

Not sure if it makes sense to set the package.json homepage to https://dxr.mozilla.org/mozilla-central/source/tools/lint/eslint/eslint-plugin-mozilla or something. I ended up reading through the current Bugzilla bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1203520) and was getting super confused by the list of comments with wrong repo names pointing to deleted repos. Or maybe if there was a definitive wiki page with some information.

Comment 1

[Greg Tatum [:gregtatum]]

I think we should update the package.json with correct information for NPM, and add a README.md to the gecko folder, then all we'd have to do is run `npm publish` inside the folder to publish any updates to npm. I was playing around a bit with this the other day, but didn't quite get it working due to my lack of knowledge on how eslint works. I can give people publish rights on NPM if they need it. We don't have any formal process around publishing...

Comment 2

[Mark Banner (:standard8)]

I'm adding a readme in bug 1314405 and updating the package.json.

Greg, I've been doing lots of work on the plugin recently, and I'm wanting to start including it in other projects, could I get access for publishing please? I'm https://www.npmjs.com/~standard8

Comment 3

[Greg Tatum [:gregtatum]]

You've been added. I see a few devtools projects using it, so you might touch base with :jdescottes when you make the changes.

Comment 4

[Mark Banner (:standard8)]

I published an update, although that is currently broken for use - see bug 1346167. I'll get a fix up for that, and hopefully publish again later today.

Comment 5

[Mark Banner (:standard8)]

0.2.29 is now on npm, with the fix for bug 1346167, which should at least make things a bit better for people using it.

Calling this fixed, as it is updated now. My plan is to try and remember to keep it up to date fairly regularly.