search

digitalthrive / Harvest

Front-end boilerplate for Gulp with everything you need to get started
MIT License
236 stars 56 forks source link

Excellent boilerplate! Any chance of turning it into an NPM package? #24

Closed michaelybecker closed 4 years ago

michaelybecker commented 8 years ago

Out of sheer laziness, more than anything - to let me (and others) be even more lazy by kickstarting a project with "npm harvest" or so instead of looking up the repo every time. Just a thought. Thanks for all your work!

ryanbenson commented 8 years ago

Thanks :) I appreciate it! Were you thinking like a global package or just tossing it up on npm so it's searchable? It's a great idea!

michaelybecker commented 8 years ago

Either way, really. personally I think I'd like to install locally anew, every project.

It would be great to jumpstart a webapp by "npm harvest (prob taken, so maybe something similar)"-ing it, and also save the extra step of re-associating the GitHub remote links.

ryanbenson commented 8 years ago

I've looked into this and thought about it, but I think this is just a lack of my knowledge but how would I go about that? I know I can drop my project up into npmjs.com and publish my package, but wouldn't that just make it available through npm install and npm search? I'm not sure that would allow someone to run npm harvest and it gives them the files.

Any suggestions? I appreciate it :)

michaelybecker commented 8 years ago

Not an npm pro myself - but according to the docs it seems like it should indeed be as simple as adding Harvest to the npm registry. In my experience there's a 1-to-1 correlation between the way a package appears on the website and its "npm install " syntax; so I'd assume that's the case. Wish I could be of more help:)

On Mon, Jul 25, 2016 at 8:33 AM, Ryan Benson notifications@github.com wrote:

I've looked into this and thought about it, but I think this is just a lack of my knowledge but how would I go about that? I know I can drop my project up into npmjs.com and publish my package, but wouldn't that just make it available through npm install and npm search? I'm not sure that would allow someone to run npm harvest and it gives them the files.

Any suggestions? I appreciate it :)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ryanbenson/Harvest/issues/24#issuecomment-234989628, or mute the thread https://github.com/notifications/unsubscribe-auth/AKfQLgQw1RyRJiAF7MpgG3M7S8KBeLezks5qZNdlgaJpZM4JRS7X .