embroider resolver favours v2 addon template over app template for routes

[void-mAlex]

given a v2 addon with a following appReeports [
... ,
'routes//*.js',
'templates//*.js',
]
with a route ./template/test.gjs (hbs works as well because they both get compiles to js files)

and an app that has its own ./template/test.hbs

you will get the addon template resolved instead of the app one even though the expectation is that the app should win

[NullVoxPopuli]

I've observed this as well

[simonihmig]

Seeing a similar thing happening for (instance-)initializers!

[kdagnan]

Seeing similar behavior for a service.

A v2 addon’s service is favored over the app’s service.ts with the same name, in the same place. Interestingly, if it’s a .js file (in the app) it’s fine.