Support for nested exposures

[DenisKent]

Hey, I would like to my MF exposes object to look like:

exposes: {
  "./components/Button": "./src/components/Button/Button.tsx",
  "./components/Input": "./src/components/Input/Input.tsx",
  "./utils/time": "./src/utils/time.tsx"
}

It doesn't work as expected, no files are created. When I run a build, I get the following message:

Skip lib\src\components\Button\Button.tsx
...

1. It might be worth showing the error message within the catch statement so the user knows why something wasn't generated.
2. The error I'm getting is: ENOENT: no such file or directory, open 'lib\dist\lib\components\Button.d.ts'. It looks to be caused by fs.writeFileSync because the \lib\components directory does not exist.

dts-loader/src/index.ts

Lines 117 to 130 in 621492b

	for (const [key, value] of Object.entries(loaderOptions.exposes)) {
	if (key && value) {
	const entryPath = path.resolve(cwd, value)
	if (entryPath === fileName) {
	const moduleFilename = `${key}.d.ts`
	const modulePath = path.resolve(
	cwd,
	`${loaderOptions.typesOutputDir}/${loaderOptions.name}`
	)
	fs.writeFileSync(
	path.resolve(modulePath, moduleFilename),
	`export * from './${path.relative(
	path.relative(cwd, modulePath),
	o.name.replace('.d.ts', '')

[ruanyl]

@DenisKent right, it doesn't expect to have a path as the exposes configuration key at the moment. I'll try to look into it

[DenisKent]

Thanks @ruanyl . Happy to work on it myself too btw. One thing that makes me hesitate is that I've not found a good way of testing updated code in action. Do you know how one might test a new branch of a webpack loader on a webpack config?

[fabiomilheiro]

I faced a similar problem but the resolution is quite simple, actually.
You can refactor your code to look like this:

exposes: {
  "./components/Button": "./src/Button.tsx", // which exports ./src/components/Button/Button.tsx
  "./components/Input": "./src/Input.tsx", // which exports ./src/components/Input/Input.tsx
  "./utils/time": "./src/time.tsx" // which exports ./src/utils/time.tsx
}

Hope it helps.

[ruanyl]

@DenisKent @fabiomilheiro Thanks for bringing this up, this is now supported in v0.1.2