Drew Neil

There's a [moderate severity advisory](https://github.com/advisories/GHSA-w8qv-6jwh-64r5) on browserslist, which is fixed by upgrading to version `4.16.5`. It would be great to see this PR merged, and a new release of `caniuse-api`...

Ok, I'm glad this is timely. I wasn't sure whether to log this as an issue on `ember-ajax` or `ember-data`. Thanks for the extra pointer about the `ajax-support` mixin. That...

To answer my own question: Yes! There is (now) [a codemod to colocate CSS modules with their components](https://github.com/phorest/ember-component-css-module-colocation-migrator). We used this at [Phorest](https://www.phorest.com/) for our Ember app, and successfully moved...

> > I should really email @tpope or something > > Or @nelstrom. If neither of these two guys know of one, then it's probably not worth knowing. :smile: Sorry,...

Most of the items in the checklist have a PR of their own. Currently, there's no PR associated with this item: - `:te` should open in split, similar to `:help`...

I'm on os x.

Note that #195 proposes a rule called `no-implicit-injections`, which sounds similar but the motivation behind it is based on recommended 'best practices', whereas this proposal is based on a deprecation.

@boris-petrov which version of Ember are you using? We are on ember-source version `3.26.1` and we still get these messages. I'm curious whether upgrading to `3.27.x` might silence these messages?

@boris-petrov ok, that gives me some motivation to upgrade.

Ah right! [ember-cli-eslint](https://github.com/ember-cli/ember-cli-eslint) and [ember-cli-template-lint](https://github.com/ember-template-lint/ember-cli-template-lint) are both marked as deprecated. As I see it, there's two ways of doing this. Either: 1. Remove the "Disable Linting" checkbox, and strip out...