Bryan Mishkin

I noticed this as part of #359 too. Let's say we have the versions `*` and `^1.2.3` present for a dependency. I'm currently leaning towards not autofixing in this situation...

For the record, I am in favor of backporting, while recognizing the extra work needed by the team to pull it off. Beyond just these particular flat config bug fixes,...

Does this help? https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/workflow.md > Running a single rule without options > > `ember-template-lint --no-config-path app/templates --rule 'no-implicit-this:error'`

> PS. In https://github.com/eslint/eslint/issues/13481, how can we get eslint-plugin-ember listed under Phase 3: Compatibility testing to raise awareness? I don't think we need the ESLint team to monitor compatibility with...

@nightire can you merge the latest master into this PR? As @ef4 said, I think it's time we proceed with this PR, even if we're not perfectly happy with the...

Can you search for `"eslint"` to make sure that it's bumped to the same v8 version everywhere? There are still fixtures it hasn't been updated in.

As mentioned by @bertdeblock, I still see `babel-eslint` in a bunch of places.

Thanks for the report! I'll definitely plan to support `exports` ASAP.

I currently have some manual logic for importing the eslint plugin package entry point which only handles `main`. We could fix it by adding logic to handle `exports` too: https://github.com/bmish/eslint-doc-generator/blob/ed310e9d0177a772b19c8390b23c33352cf45882/lib/package-json.ts#L27...

To be clear, you're not doing anything wrong, we definitely want to handle both CJS/ESM ESLint plugins (using either `main` or `exports`). Node will automatically find/load a package's entry point...