"nextein build" not working on Windows with Next11, Webpack5 & Nextein3

[matthiasprieth]

Hi @elmasse, I'm getting this error after upgrading to next@11.0.1, Webpack@v5 & nextein@3.1.2

info  - Creating an optimized production build
Failed to compile.

C:UsersMatthiasDocumentsproject-nextjs
ode_modules
exteindistpluginsinternalsmarkdown/render
Module build failed: UnhandledSchemeError: Reading from "C:UsersMatthiasDocumentsproject-nextjs
ode_modules
exteindistpluginsinternalsmarkdown/render" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "c:" URIs.

> Build error occurred
Error: > Build failed because of webpack errors
    at C:\Users\Matthias\Documents\project-nextjs\node_modules\next\dist\build\index.js:15:924
    at async Span.traceAsyncFn (C:\Users\Matthias\Documents\project-nextjs\node_modules\next\dist\telemetry\trace\trace.js:6:584)

As you can see slashes "/" are missing in the windows path. When I switch back to nextein@2.7.3 I don't get this error. Do you think this issue is related to Nextein or a problem/misonfiguration in Webpack5? Sorry that I can't share an example project :(

[elmasse]

@matthiasprieth thanks for reporting this issue.

I have done a quick test using the nextein-starter and I was able to reproduce the issue on Windows 10. It seems to be related to a change introduced in v3. I'll get it fixed today.

Sorry for this inconvenience and thanks for using nextein! Max

[elmasse]

@matthiasprieth this should be fixed in v3.1.3

Please let me know if you have a chance to test it.

Thanks!

[matthiasprieth]

Hi @elmasse , thank you so much for this quick fix! Works like a charm now! 👍 If I encounter any problem, I'll let you know, but it looks very promising!