suggested fix for issue #74564

[chrisweb]

Fixes #74564

The idea for the fix is from fbf9e12#diff-907b7be0cfc75bd37773e5ebc38d1deffa40861b8ac1cde92e4992e284a1ee59R1221 I use the same nodejs pathToFileURL (https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/find-config.ts#L74)

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: 10634ba

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: 85d7036

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[himself65]

I think you just need pathToFileURL(path) here?

[chrisweb]

I had forgotten to add the require for pathToFile which I fixed just now.

Regarding your comment, I'm not sure I understand what you suggest. I mean I'm not sure to what line of the code your comment is referring. Do you mean moving pathToFileURL into the interopDefault function?

Do you mean using pathToFileUrl without also using "require.resolve"?

• the importPlugin function gets the plugin value (and the project root path)
• the plugin value is an array, where the first value is the mdx plugin name (the package name) as a string and the second value (which is optional) contains the plugin options (which need to be serializable)
• using require.resolve we get the path of the plugin (package) by passing the name and project root path
• then comes my change which fixes the path we get from previous step and turns it into a windows file URL using pathToFileURL (if the platform is windows)
• now the import function is not throwing an error anymore (on windows) because the value we pass to import is now a valid file:// URL and not a string like 'c:/PATH_TO_ESM_PACKAGE'