This package depends on [email protected]. However, the mime package frequently updates the patch number to pull in additional mime types, without changing the API. (At this time, it's at v1.2.7.)
While it makes sense to lock down a deployed application or website, perhaps even using git or npm shrinkwrap, a reusable library like form-data should be a bit more flexible.
Consider switching the dependency to ~1.2.7 so that users can add additional mime types without having to bundle and patch form-data.
Similarly, the async project is extremely stable at this point. The API has been consistent for about a year, and only minor bug fixes have been applied. The last few versions have fixed some inconsistencies between null/undefined usage, added a bunch of tests, and cleaned up the readme. Consider using ~0.1.22 to be able to work with these changes.
This package depends on
[email protected]. However, the mime package frequently updates the patch number to pull in additional mime types, without changing the API. (At this time, it's at v1.2.7.)While it makes sense to lock down a deployed application or website, perhaps even using git or
npm shrinkwrap, a reusable library like form-data should be a bit more flexible.Consider switching the dependency to
~1.2.7so that users can add additional mime types without having to bundle and patch form-data.Similarly, the async project is extremely stable at this point. The API has been consistent for about a year, and only minor bug fixes have been applied. The last few versions have fixed some inconsistencies between null/undefined usage, added a bunch of tests, and cleaned up the readme. Consider using
~0.1.22to be able to work with these changes.