Before I was using aldeed:simple-schema package, then switched to the npm version and removed the package:
meteor remove aldeed:simple-schema
However when Meteor starts building, it reinstals the package, because of an indirect dependency on it from another package.
Is there a convenient way to identify the package introducing the indirect dependency?
Here is the content of the “packages” file:
firstname.lastname@example.org # Packages every Meteor app needs to have
email@example.com # Packages for a great mobile UX
firstname.lastname@example.org # The database Meteor supports right now
email@example.com # Compile .html files into Meteor Blaze views
firstname.lastname@example.org # Reactive variable for tracker
email@example.com # Meteor’s client-side reactive programming library
firstname.lastname@example.org # CSS minifier run for production mode
email@example.com # JS minifier run for production mode
firstname.lastname@example.org # ECMAScript 5 compatibility for older browsers.
email@example.com # Enable ECMAScript2015+ syntax in app code