refactor: avoid semver where possible#1309
Conversation
JustinBeckwith
left a comment
There was a problem hiding this comment.
Thanks for this! I'm curious - did you see other places we were using the module? Wondering if we can remove it from package.json all together.
|
👋 most folks do not have I'd be open to dropping the SemVer dependency, but I would want to see it instead replaced with logic that checks the major version, like this. |
|
@TrySound this has stalled for a little while, did you have any interested in updating the PR to still throw on unsupported engine versions? |
|
Oops, sorry. Forgot about it. Will update today. |
Checking node version is not necessary anymore with "engines" field in package.json which prevents from installing this package with legacy node.
c92986a to
8a82f78
Compare
|
@TrySound looks reasonable to me, could I just bother you to run |
|
|
Hm... fix does not have any effect |
🤖 I have created a release \*beep\* \*boop\* --- ### [5.1.2](https://www.github.com/googleapis/cloud-trace-nodejs/compare/v5.1.1...v5.1.2) (2021-02-04) ### Performance Improvements * **deps:** avoid semver where possible ([#1309](https://www.github.com/googleapis/cloud-trace-nodejs/issues/1309)) ([4c05cae](https://www.github.com/googleapis/cloud-trace-nodejs/commit/4c05caeb3910657b3eb413da61aac03cb321bd7b)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Checking node version is not necessary anymore with "engines" field in
package.json which prevents from installing this package with legacy node.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕