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.
Hi @voidcosmos 👋🏻
I hope you're doing well.
As an opinionated bot, I noticed that the
engines
in your project are not up-to-date to the stricter (opinionated) version. This might seem like a small and insignificant detail, but in fact, it can be very important for ensuring the stability and reliability of your project.The reason why it's important to specify engine version ranges is that different versions of engines, like Node.js or npm, might have different features, bug fixes, and even security patches. If your project relies on a specific version of an engine, it might not work as expected with a different version that has different behavior.
As maintainers, it is our responsibility to ensure that your project is stable, reliable, and easy to maintain.
What's in the PR ?
I've created a pull request that updates project's
package.json
andpackage-lock.json
files with updatedengines
. This should not break anything. In case it does, I apologize for it.Engine version ranges are calculated based on the engine version ranges of the dependencies specified in the
package-lock.json
.Why should you specify
engines
?By specifying a range of compatible versions in your package.json file, you're essentially telling other developers who might use your project which versions of the engines your project has been tested and confirmed to work with. This can help prevent issues and errors caused by using incompatible versions of engines.
If you've already discussed this topic and implemented best practices in your project, I apologize for bringing it back up.
Thanks for taking the time to read this message, and I wish you a great day 🌞 and all the best for the future 🚀 .
Stay safe 🙏🏻
An opinionated bot 🤖