Glint v2

[NullVoxPopuli]

This is not ready for merge, and just for demonstration right now.

If folks have eliminated their hbs, they can have a far superior TS experience by doing the changes in this PR to their app.

Why can't we merge this?

Glint V2 does not support hbs, and the current iteration of the app blueprint must support hbs.

More on this later.

[void-mAlex]

docs say this needs to be under deps not devDeps
https://github.com/typed-ember/glint/blob/main/docs/v2-upgrade.md#step-2-upgrade-glinttemplate-to-the-latest-npm-version

[NullVoxPopuli]

devDeps is correct tho

[urbany]

can we remove ember-template-lint since hbs is no longer supported?

[NullVoxPopuli]

Nay, we still use it for the template blocks in a gjs/gts file.

There is an effort to port over all the lints from template to the eslint plugin, tho. When that finishes (want to help? <3) we can remove template-lint

[urbany]

@NullVoxPopuli ah ok, and these lines still make sense? will they lint the gj and gts files?

    "lint:hbs": "ember-template-lint .",
    "lint:hbs:fix": "ember-template-lint . --fix",

[NullVoxPopuli]

ye

there is an even option you can set in the templatelint config to disable checking of js/ts (like, old-style tests with hbs)

'use strict';
module.exports = {
  extends: 'recommended',
  checkHbsTemplateLiterals: false,
};

this isn't required and is only a minor perf improvement for template-lint speed