$ npm ls strong-globalize
@loopback/example-todo@2.0.0 /private/tmp/loopback4-example-todo
├─┬ @loopback/repository@1.19.1
│ └─┬ loopback-datasource-juggler@4.18.1
│ ├─┬ loopback-connector@4.10.1
│ │ └── strong-globalize@5.0.5 deduped
│ └── strong-globalize@5.0.5
├─┬ @loopback/rest@2.0.0
│ └─┬ strong-error-handler@3.4.0
│ └── strong-globalize@5.0.5 deduped
└─┬ loopback-connector-rest@3.6.0
└── strong-globalize@4.1.3
Let's upgrade strong-globalize to the latest version in LB modules maintained by StrongLoop (unless they are in Active or Maintenance LTS mode).
In a typical application, there are multiple versions (and copies) of strong-globalize in the dependency tree.
Take our examples/todo as an example:
At the moment,
require('strong-globalize')is taking about0.3s(see strongloop/strong-globalize#158). Every copy of the module adds another 1/3 of a second to the application load time.Let's upgrade strong-globalize to the latest version in LB modules maintained by StrongLoop (unless they are in Active or Maintenance LTS mode).
Acceptance criteria
Figure out a solution for the node version's compatibility first, see comment Upgrade strong-globalize to the latest version #4585 (comment)
Check the following packages and update strong-globalize dependency if needed. The list is based on https://github.com/strongloop-internal/scrum-apex/issues/372:
Connectors
Others