Respect existing package.json?

[binarykitchen]

Hello again

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

[binarykitchen]

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

[RyanMcG]

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

[RyanMcG]

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]

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]

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.