Remove react-meteor-data's dependency on check-npm-dependencies #268
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.
Removes the dependency on
tmeasday:check-npm-versions. This will save ~10kb in the bundle payload and save a small runtime cost.An argument can be made that
check-npm-modulesdoesn't provide much value when compared to what the Meteor build tool already does. Without this, Meteor will already display an error messageIn my opinion, that is clear enough and the error provided by check-npm-versions doesn't provide much more insight - at least not enough to warrant the weight it adds to the production build. Furthermore, if you are using this package, it is very likely that you already have
reactinstalled; I can't imagine a developer getting very far without havingreactinstalled... at least not far enough to usewithTrackerin any capacity.Whilst it is nice to get this error at build time during development, I don't think the tradeoff is worth it, especially considering that it would only be helpful in very rare circumstances.