Bert De Block

Results 232 comments of Bert De Block
trafficstars

FWIW, the `outputPaths` option is deprecated as of v5.3.0

FYI, the `unbound` helper was never deprecated nor removed, so I think the [no-unbound](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-unbound.md) rule is still relevant.

I'm not sure if I'm following. I can't seem to understand why a QUnit chunk should be created for a production build. The chunk is unused as well. Is something...

I created [bertdeblock/ember-auto-import-525-repro](https://github.com/bertdeblock/ember-auto-import-525-repro). It's a fresh `v4.6.0` app. I also included the `dist` folder which is the result of running `ember build --environment=production`. The QUnit chunks are: - [chunk.916.74986bc5e3f10f749eff.js](https://github.com/bertdeblock/ember-auto-import-525-repro/blob/main/dist/assets/chunk.916.74986bc5e3f10f749eff.js) -...

@void-mAlex, in my test, the chunk is only created, but not included in `index.html`, so it won't be requested by the end user. This is the case for your app?

Could it be that maybe you are importing/including test-related code in the app itself somehow? With a fresh app, I only observed the chunk being made, but _not_ included in...

I'm interested in this as well.

@rami-alloush No, at the moment, it's not. @kellyselden Did you manage to figure out what was causing this?

https://github.com/ember-cli/ember-cli/issues/9528 seems like the same issue and https://github.com/ember-cli/broccoli-asset-rewrite/pull/73 was made as an attempt to fix it.

The ESLint issue is because something is pulling in an older version of ESLint which doesn't recognise the `overrides[0].extends` key. I've seen this happen when people were still using `ember-cli-eslint`....