Custom component utility for type-safe props causing importMap generation error.

[revnelson]

Array Row Labels are something we use in many places in our config. We made a utility function to reduce boilerplate of typing out the path, clientProps, and exportName in all these places, as well as give us type safety for possible clientProps. Here is that utility, for reference:

import type { RowLabelComponent } from "payload"

type ArrayRowLabelProps = {
	labelKey?: string
	labelParent?: string
	fallback?: string
	employee?: boolean
	selectField?: string
}

export const AdminRowLabelConfig = (
	clientProps?: ArrayRowLabelProps
): RowLabelComponent => ({
	clientProps,
	path: "/components/ArrayRowLabel",
	exportName: "ArrayRowLabel"
})

However, importing this utility anywhere in our config throws the dreaded CSS error when generating the importMap.

In troubleshooting, I have found by writing this utility directly in the config (instead of importing it) that there is nothing wrong with the utility itself. This, however, negates the usefulness of using it anywhere in our config. I don't have a clear understanding of how the importMap generation works, but it seems like there is a step within that generation that doesn't handle this import well.

Is there some way I can modify our utility or bundling configuration to make this work?

[revnelson]

Does this have something to do with tsc compiling? Do I need to add a copyfile step before generating importMap? A nudge in some direction would be greatly appreciated here.

[revnelson]

It doesn't seem to have anything to do with typescript; I removed the types and renamed the file with a .js file extension and am still running into the issue.

[revnelson]

At a loss here, and any help would be greatly appreciated.

[revnelson]

Still stuck getting the Unknown file extension ".css" for ReactCrop.css error on v3.36.1.