Moved npm dependencies to devDependencies #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not sure how knowledgable you are on npm design patterns.
I installed this package using
npm install nwcell/ics.js
but it came with a lot of stuff I don't need in production. Obviously I don't need grunt or bower or the libraries you hard-coded into the distribution files in order to consume your library. I only need those dependencies if I want to develop your package itself. Therefore I've moved those dependencies down.If you want to be consumed by node but not hard-code the third party packages, I would keep
file-saver
as a production dependency and use something likerollup
orbrowserify
or something to distribute.