[ ] I've ensured the unit and smoke tests are still passing - either by running yarn test:unit and yarn test:smoke:[ios|android] or by checking the appropriate CircleCI builds' statuses.
[ ] I've manually tested whether the changes I made work as expected.
Motivation and Context
update node-forge to 0.10.0
closes #324
Description
check with yarn why which packages are using older version of node-forge
remove from yarn.lock entries referring to node-forge, google-p12-pem, selfsigned
run yarn install
Test plan
yarn why node-forge
yarn why v1.22.0
[1/4] Why do we have the module "node-forge"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "node-forge@0.10.0"
info Reasons this module exists
- "@expo#xdl" depends on it
- Hoisted from "@expo#xdl#node-forge"
- Hoisted from "@expo#xdl#webpack-dev-server#selfsigned#node-forge"
- Hoisted from "@google-cloud#logging-bunyan#google-auth-library#gtoken#google-p12-pem#node-forge"
info Disk size without dependencies: "1.77MB"
info Disk size with unique dependencies: "1.77MB"
info Disk size with transitive dependencies: "1.77MB"
info Number of shared dependencies: 0
Done in 0.72s.
Checklist
yarn test:unit
andyarn test:smoke:[ios|android]
or by checking the appropriate CircleCI builds' statuses.Motivation and Context
update node-forge to 0.10.0 closes #324
Description
Test plan