On 06/28/2015 11:09 PM, Andrew Udvare wrote:
I would still find it useful to install CoffeeScript (among others like
PhantomJS) via Portage for global use. Right now I hack on
~/node_modules/.bin to PATH in my shell (luckily that works).
It doesn't look like anyone wants to get involved with
On Sun, 28 Jun 2015 12:30:25 -0400
Michael Orlitzky m...@gentoo.org wrote:
I recently found a need for the CoffeeScript compiler[0] that runs on
top of NodeJS. Its test suite requires a bunch of other javascript
packages, and I wound up packaging enough of them to test
CoffeeScript.
In the
On 06/30/2015 03:56 AM, Ian Delaney wrote:
Is this what I prompted about a year or more ago, and drew no interest
in pursuing the npm path? I cited an eclass called npm.eclass in a
dev's overlay. The conclusion was that using npm to install anything
competed with portage at a level that
FWIW, I also bumped into this in my previous job.
I even wrote this (https://github.com/neurogeek/g-npm) which is incomplete
but saved me a bunch of time creating a crazy amount of npm ebuilds.
kinda rant
My experience is, this isn't worth it. npm is a mess, is
maintainer-unfriendly (although it
I recently found a need for the CoffeeScript compiler[0] that runs on
top of NodeJS. Its test suite requires a bunch of other javascript
packages, and I wound up packaging enough of them to test CoffeeScript.
In the process I wrote an eclass to handle packages hosted on the npm
registry[1] and
On 2015-06-28, at 09:30, Michael Orlitzky m...@gentoo.org wrote:
https://github.com/orlitzky/npm https://github.com/orlitzky/npmWe don't
have any standalone javascript packages in the tree at the
moment but I know there's been some interest before. Is anyone still
(planning on) working
