Brad Overton

> Right now, it seem when we do corepack enable in one repo it enables it for all the repos which share the same version of node. I'm using pnpm...

Unfortunately some repos in my organisation will likely continue using yarn/pnpm plugins, so I don't think that will work for us.

We found this occurred specifically in our CI environment, when CI=true

Some starting points for investigation CI flags look to be used here https://github.com/emberjs/ember-cli-babel/blob/b61e71bfa923fc3d9aca9c3639ed6946e7ba8c68/lib/ember-plugins.js#L12 https://github.com/emberjs/ember-cli-babel/blob/b61e71bfa923fc3d9aca9c3639ed6946e7ba8c68/lib/babel-options-util.js#L66 From https://github.com/ember-cli/babel-plugin-debug-macros/tree/master > The assert macro can expand in a more intelligent way with the correct...

Looks like it has been reported over there as an issue https://github.com/ember-cli/babel-plugin-debug-macros/issues/89

Feels like a lot of work throughout the ecosystem for little gain. Whole new syntax, would need guides, linting updates.. I like that `on` being presented as _just a modifier_...

Looking forward to this as well. For what it's worth, we have 300+ GTS files in a private repo.

Still exists on ubuntu/chrome 108 > Is it suffient for you to wrap the error in a try-catch? Or does it actually break some behaviour? See Wrapping in a try/catch...

There's also a very good jsfiddle from this PR https://github.com/highcharts/highcharts/issues/17533 demonstrating the issue http://jsfiddle.net/t0pn9c27/

It looks like everyone in this thread is also experiencing the same issue, but with pnpm https://github.com/gitKrystan/prettier-plugin-ember-template-tag/issues/38 That plugin is meant to be registered for gts/gjs extensions, but seems to...