warning " > node-yaml@4.0.1" has incorrect peer dependency "js-yaml@^3.13.x".
warning " > protoc-gen-ts@0.8.2" has unmet peer dependency "google-protobuf@^3.13.0".
Updated package.json to use dependency versions that don't produce the warnings.
One questionable thing is that I had to revert the version of package js-yaml : we specify node-yaml version 4.0.1 which has js-yaml 3.14.1 as a peer dependency. We were specifying 4.1.0, hence the warning. I checked our source code and do not see anywhere that we use this package as a direct dependency, so assume this is ok.
yarn produced these warnings:
```
warning " > node-yaml@4.0.1" has incorrect peer dependency "js-yaml@^3.13.x".
warning " > protoc-gen-ts@0.8.2" has unmet peer dependency "google-protobuf@^3.13.0".
```
Updated `package.json` to use dependency versions that don't produce the warnings.
One questionable thing is that I had to _revert_ the version of package js-yaml : we specify `node-yaml` version 4.0.1 which has js-yaml 3.14.1 as a peer dependency. We were specifying 4.1.0, hence the warning. I checked our source code and do not see anywhere that we use this package as a direct dependency, so assume this is ok.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
yarn produced these warnings:
Updated
package.jsonto use dependency versions that don't produce the warnings.One questionable thing is that I had to revert the version of package js-yaml : we specify
node-yamlversion 4.0.1 which has js-yaml 3.14.1 as a peer dependency. We were specifying 4.1.0, hence the warning. I checked our source code and do not see anywhere that we use this package as a direct dependency, so assume this is ok.roysc referenced this pull request from cerc-io/laconicd-deprecated2023-09-25 12:36:30 +00:00