Bert De Block

I think in this case, the solution would be to, either define some argument types, or comment out / remove `Args: {}` from the signature, indicating that the component does...

Feel free to make a PR over in `ember-source`. The `component` blueprint is located there, not in the `ember-cli` repo.

Seems "fixed" since we've enabled the `EMBER_TYPESCRIPT_BLUEPRINTS` flag by default.

I think we can close this. The deprecation is documented here: https://deprecations.emberjs.com/v3.x#toc_setting-on-hash.

At the moment, we ditched `ember-cli-deprecation-workflow` in favour of a custom / smaller / more vanilla setup: ```js // app/app.js import { importSync, isDevelopingApp, macroCondition } from '@embroider/macros'; if (macroCondition(isDevelopingApp()))...

Could you maybe deprecate v6.0.0 specifically on npm and remove [v6.0.1](https://ember-intl.github.io/ember-intl/versions/v6.0.1) from the docs?

@NullVoxPopuli Going to close this one in favor of #10141 if that's okay.

The parser in the ESLint config file is still `babel-eslint` and `babel-eslint` is still included in `package.json`. Note that we now also need to take the `typescript` flag into account,...

Resolved by https://github.com/ember-cli/ember-cli/pull/10287 I think.

Closing. This was covered in https://github.com/ember-cli/ember-cli/pull/8878.