fix: remove engines field #155
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When the current node version does not meet the engines field requirement npm warns but yarn errors. Nothing in this module requires node 18+ so remove the engines field. Refs: ipfs/aegir#1276
github-actions bot
pushed a commit
that referenced
this pull request
May 17, 2023
## [12.1.3](v12.1.2...v12.1.3) (2023-05-17) ### Bug Fixes * remove engines field ([#155](#155)) ([a464023](a464023))
|
🎉 This PR is included in version 12.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the current node version does not meet the engines field requirement npm warns but yarn errors.
Nothing in this module requires node 18+ so remove the engines field.
Refs: ipfs/aegir#1276
Fixes: #154