Is your feature request related to a problem? Please describe
In my component's props TS interface, I can use JSDoc comments to set the description, and can even use the @default tag to describe the default value 💯
However, nothing happens when I use the @deprecated tag.

Describe the solution you'd like
Some ideas:

• It would be nice i

Issue Summary

When running under Node 14, the error message printed out when a second instance of Ghost is trying to bind to a port isn't the custom one we have, but the generic one.

To Reproduce

1. Use Node 14
2. Run an instance of Ghost
3. Attempt to run another instance of Ghost on the same port
4. 💥

We have a check like error.errno === 'EADDRINUSE', which evals to `fa

By default ember-cli updates a number of the "app trees" to be from tests/dummy when developing an addon locally. We do this for app, styles, templates, public, and tests trees (handled inside lib/broccoli/ember-addon.js).

Unfortunately, we do not forward the apps vendor tree to tests/dummy/. This means that our addon's treeForVendor is called, but then subsequently clobbered by the "apps

Relevant conversation here: hjdivad/ember-m3#807

It got lost early in some v4 release candidate. Original content could be found here: https://github.com/kaliber5/ember-bootstrap/blob/b711738bba95fd9523e573e5e314f4cf7257f93f/addon/components/base/bs-button.js#L183-L191 It could be used as a starter.

Reported by @rwwagner90 here: kaliber5/ember-bootstrap#1110 (comment)