i have to ignore this package from automatic updates because it doesn't use semver, so if you are going to update it I'd appreciate if you stuck to the same scheme that every other package in the entire world uses, including other packages from this organization. Since the package didn't communicate that it was locked into Mongoose v6 (had to look back in the changelog for several versions), it broke a ton of tests for really weird reasons that took a while to figure out.
On the other hand, we're actually trying to remove all usage of this package in our codebase since it's so dangerous to use. It's especially alluring to inexperienced programmers who don't want to have to type populate() all the time, but at scale it creates a ton of performance problems that end up resulting in removal of the plugin entirely. So if you don't want to maintain it anymore, I would also advocate for archival and a note saying "please stop using this".
i have to ignore this package from automatic updates because it doesn't use semver, so if you are going to update it I'd appreciate if you stuck to the same scheme that every other package in the entire world uses, including other packages from this organization. Since the package didn't communicate that it was locked into Mongoose v6 (had to look back in the changelog for several versions), it broke a ton of tests for really weird reasons that took a while to figure out.
On the other hand, we're actually trying to remove all usage of this package in our codebase since it's so dangerous to use. It's especially alluring to inexperienced programmers who don't want to have to type
populate()
all the time, but at scale it creates a ton of performance problems that end up resulting in removal of the plugin entirely. So if you don't want to maintain it anymore, I would also advocate for archival and a note saying "please stop using this".