opened
raymondfeng
username_0
This PR renames the following packages to be consistent with other extension modules.

- @loopback/extension-health => @loopback/health
- @loopback/extension-logging => @loopback/logging
- @loopback/extension-metrics => @loopback/metrics

## Checklist

- [x] DCO (Developer Certificate of Origin) [signed in all commits](https://loopback.io/doc/en/contrib/code-contrib.html)
- [x] `npm test` passes on your machine
- [ ] New tests added or existing tests modified to cover all changes
- [x] Code conforms with the [style guide](http://loopback.io/doc/en/contrib/style-guide.html)
- [ ] API Documentation in code was updated
- [x] Documentation in [/docs/site](../tree/master/docs/site) was updated
- [x] Affected artifact templates in `packages/cli` were updated
- [x] Affected example projects in `examples/*` were updated

👉 [Check out how to submit a PR](https://loopback.io/doc/en/lb4/submitting_a_pr.html) 👈
refactor: rename `@loopback/extension-*` packages
issue
created
bajtos
username_1
+1 to rename extensions for consistency.

How are users of the existing packages going to learn about the new name? Have you considered deprecating the old packages with a message pointing users to the new name? Example:

https://www.npmjs.com/package/shot

In the past, we published a new version of the old package with a short readme pointing users to the new one, see https://www.npmjs.com/package/loopback-explorer
comment
created
raymondfeng
username_0
@username_1 Here is my plan.

1. We'll publish a new release to include the renamed packages 
2. We'll add `deprecation` messages to existing `@loopback/extension-*` npm packages using `npm deprecate` to remind our users to upgrade.
comment