Closed Bug 994422 Opened 11 years ago Closed 11 years ago

package.json should add keywords if we're planning on releasing this via npm

Categories

(Hello (Loop) :: Client, defect)

Product:
Hello (Loop)
Component:
Client
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Blocking Flags:
backlog backlog+

People

(Reporter: pdehaan, Unassigned)

Details

(Whiteboard: [tech-debt])

https://github.com/mozilla/loop-client/blob/master/package.json is missing a few suggested fields (I'll file a PR for that shortly), but once that lands we (not me) should add some good keywords for this. I can only think of "webrtc" but there are probably others you may want to add). Also, I'm a bit confused re: "engines". Currently the lastest version of Node.js is 0.10.26 which comes bundled w/ npm 1.4.3. Not sure if that could cause any issues with `engines` which defines an npm version of "1.3.x".
I think we're highly unlikely to release loop-client via npm, especially as the main intent of this repo is for web content only. The only reason it has node is so that we could easily serve the pages to developers. The actual hosting solution is likely to be something different.
Whiteboard: [tech-debt]
backlog: --- → Fx36+
backlog: Fx36+ → Fx37+
backlog: Fx37+ → backlog
We're not planning on releasing as an npm - there's no real reason for it to be at the moment, and the npm infrastructure is more for development. Hence won't fix.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.