Closed
Bug 1082288
Opened 11 years ago
Closed 10 years ago
Why is Fireplace a "private" repo on npm?
Categories
(Marketplace Graveyard :: Code Quality, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cvan, Unassigned)
References
Details
(Whiteboard: [marketplace-transition])
https://github.com/mozilla/fireplace/blob/e53ad4/package.json#L4
> {
> "name": "fireplace",
> "version": "1.1.0",
> "private": true,
> ...
> }
Why shouldn't Fireplace be published on npm?
`npm install fireplace` would be nice.
|
||
Comment 1•11 years ago
|
||
I plan on publishing Fireplace on bower so other projects can re-use its CSS and some of its modules, but I don't know about having it on npm since there are no Node scripts.
|
||
Comment 2•11 years ago
|
||
Bear in mind: fireplace is this https://www.npmjs.org/package/fireplace
Whats the real question here? Should fireplace be on npm?
Status: NEW → UNCONFIRMED
Ever confirmed: false
Priority: -- → P4
|
||
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Whiteboard: [marketplace-transition]
You need to log in
before you can comment on or make changes to this bug.
Description
•