RyanMcG / lein-npm

Manage Node dependencies for CLJS projects
295 stars 43 forks source link

Respect existing package.json? #23

Open binarykitchen opened 9 years ago

binarykitchen commented 9 years ago

Hello again

Any chance this plugin could respect any existing package.json if there are any? This instead of creating a temporary one.

binarykitchen commented 9 years ago

Reason is because I want to use https://www.npmjs.com/package/gulp-load-plugins and it cannot parse project.clj ...

RyanMcG commented 9 years ago

Maybe! I'm interested in design ideas or a PR!

RyanMcG commented 9 years ago

Do you mean persist package.json instead of creating an ephemeral version or do you mean only modify dependencies section of an existing package.json?

Would #35 help? I'm trying to decide what behaviour is best.

binarykitchen commented 9 years ago

yep, don't create an epheremal package.json when there is already one. in our project we use leiningen and node.js/io.js together and run the one or other engine, depending on the environment.

RyanMcG commented 7 years ago

Take a look at #53. I don't think it's really what you want, but let me know if it would help or hurt your use-case.