I often encounter this problem - the ecosystem of the package makes it easy to do everything, but not always well. Usually I clone a package into my own packages folder in the meteorite project folder, make changes, and then send the download request to the original author so that the changes make their way to other people. With a package of check-argument-check in your project, this usually involves adding a control package to the packages.js file using api.use ('check'), and then defining methods for checking the parameters.
source share