Module not found: Error: bug: embroider resolver's meta is not propagating

[gossi]

I'm running into this error:

Module not found: Error: bug: embroider resolver's meta is not propagating

The main idea was to use webpack.resolve.alias to point to code that I moved somewhere else.

Repro:

• Branch: https://github.com/gossi/unidancing/tree/re-architecture
• Commit: https://github.com/gossi/unidancing/tree/d28a643e21289054699ca8f8f25f38fa4c30c2fb

After checkout:

pnpm install
cd web/
pnpm test:prebuild
pnpm start

POI in the code:

• The main folder is web/app/domain/ where I moved my code into
• The webpack config found in web/ember-cli-build.js for the alias
• The ts config: web/tsconfig.ts with its paths which made it possible at first at least in the editor

I traced it here:

embroider/packages/core/src/module-resolver.ts

Lines 1058 to 1065 in 289f83d

	if (movedPkg !== pkg) {
	let originalFromFile = request.meta?.originalFromFile;
	if (typeof originalFromFile !== 'string') {
	throw new Error(`bug: embroider resolver's meta is not propagating`);
	}
	request = request.rehome(originalFromFile);
	pkg = movedPkg;
	}

And with a bit more debug, I figured it was coming from this file: web/app/domain/supporting/tina/index.ts, which when renamed into index.gts it worked.

Which is weird, because on node_modules/.embroider/rewritten-app I can see, the gts files are already correctly transpiled to .ts (using template() from @ember/template-compiler).

[gossi]

Oh, renaming ts files that re-export gts files to gts, aka index.ts -> index.gts. Then I run into very unreliable errors:

Renaming this from ts to gts... is only a patch, and not even a helpful one. It seems like it is only forwarding the issue to another problem, which is described in detail in #1800 (with a reproduction).