Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The manifest is optional, so for big projects I would probably recommend using a manifest to keep all your versioning in one place.

Duo falls back to the manifest if it cannot resolve the path on it's own.

For proof of concepts and hacks though, adding a manifest is a waste of everyone's time.



I personally haven't had much trouble with:

  npm install foo --save-dev
When you go beyond a single developer playing around, having a quick, well-known place to look to learn what dependencies are being used is very useful.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: