Bryan Mishkin

The goal is to match ESLint behavior so this sounds like an important fix to make.

Very much in favor of supporting the same automated "suggestions" feature that ESLint has.

Looks like it specifically doesn't like the two consecutive single-character words: `word a b word` As @mongoose700 said, it sounds like from the doc for [no-whitespace-within-word](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-whitespace-within-word.md) that it may not...

@SkoebaSteve I think ESLint's behavior would actually work for you: I tested with ESLint and any file matching a glob passed to ESLint will be linted, not limited to predefined...

Good catch, we definitely want this to exit with failure.

I tested this out in a brand-new Ember app and saw the correct exit code: ``` ~/Development/ember-test-app main * yarn lint:hbs yarn run v1.22.18 $ ember-template-lint . ember-test-app/node_modules/ember-template-lint/lib/get-config.js:146 throw new...

CC: @VincentMolinie

Mid-2022 so we can drop support for Node versions that will end-of-life around then, assuming we have enough breaking changes compiled.

I would prefer we have a separate PR for each breaking change. That way, we have smaller, simpler PRs and each change will show up nicely as a separate item...

I would like to start preparing for this release soon. Any other breaking changes we should include? The current list has some straightforward rule / config changes but also some...