search

unit9 / coffee-bone

49 stars 7 forks source link

NPM module #6

Open silviopaganini opened 9 years ago

silviopaganini commented 9 years ago

can we make this a NPM package/module so it's easier to install?

better than a "clone this into your folder" ...

rollcat commented 9 years ago

+1, the best way to deal with libraries

naso commented 9 years ago

https://www.npmjs.org/package/coffeebone

Not fully done yet, as I need to research a way of when you do npm install coffeebone it installs things in the root and not inside a node_modules folder. If there is no standard way then we do a script and put it on main: attribute inside package.json.

Also there's a typo on README and I would consider change the name as there is a yeoman-coffee-bone module already.

silviopaganini commented 9 years ago

Hmmm no need to be a yeoman grnerator really. Just a easy way to install would do the job

On Friday, 10 October 2014, Fábio Azevedo notifications@github.com wrote:

https://www.npmjs.org/package/coffeebone

Not fully done yet, as I need to research a way of when you do npm install coffeebone it installs things in the root and not inside a node_modules folder. If there is no standard way then we do a script and put it on main: attribute inside package.json.

Also there's a typo on README and I would consider change the name as there is a yeoman-coffee-bone module already.

— Reply to this email directly or view it on GitHub https://github.com/unit9/coffee-bone/issues/6#issuecomment-58698801.

sent.from.mobile

@silviopaganini +44 753 4915 733

naso commented 9 years ago

Didn't mean that.

There's a package already with coffeebone in the name. Shall we get a different name?

https://www.npmjs.org/search?q=coffeebone

naso commented 9 years ago

Done.

http://browsenpm.org/package/coffeebone

This was the only way I managed to have it working as expected. Check README for instructions.

neilcarpenter commented 9 years ago

Forgot about this! Whoopsie

The idea of making this easier to install I guess is a valid one, I don't really think npm is the right delivery mechanism though - it's really for serving module dependencies to node (and now browserify) apps, it is used to include things in existing projects, not scaffold a new one. Hence the node script to copy files and recursively remove itself to make this work...

But having said this I can't think of a more suitable solution really.. Could use bower which is more general-FE, as opposed to JS-specific (npm), but would still have the same issue of having to copy files from bower_components instead of node_modules, so no difference really, and better to only have one CLI dependency than two...

Also, not sure if there would be any issues with this install script if running from a globally installed copy of coffee-bone... I think on the off-chance you installed with -g then the install script might not work... But probably not worth doing anything about, just mention in README or something.

ALSO, @naso did you check to see who took the name already?! https://www.npmjs.org/package/coffee-bone I published and then unpublished to test it out :grin: Can try and republish under the original name when I get a minute.

naso commented 9 years ago

Agree, although decided to move on with the idea using the node script to "fix" the structure, so one day npm might have a standard solution for this kind of things. I would call this more of package than module.

Also agree, that mentioning in the README to doesn't install it globally is enough.

Ah my bad, I misunderstood the documentation, and thought they were discouraging the use of "-" in the name. Feel free to publish it under the original name and let me know and will un-publish mine.