Open VityaSchel opened 2 days ago
For your information, I'm running this on macOS, but this shouldn't make any difference because I saw person with the same problem on Windows
set manifest: false on the plugin for now as workaround
@VityaSchel example seems to work for me. Supply a repo that reproduces the issue
Hello @VityaSchel. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction
will be closed if they have no activity within 5 days.
@VityaSchel example seems to work for me. Supply a repo that reproduces the issue
it does not matter which project you take, the problem is in path, you can run empty project with spaces in path to it
i did and it worked. Supply a repo broken from the start
i did and it worked. Supply a repo broken from the start
example repo with nextjs v14 does not work in my case with bun.sh if you can't reproduce and won't fix this, you can close this, it still will be a starting point for developers who have the same issue
Describe the bug
I spent 3 hours figuring out why your example https://github.com/module-federation/module-federation-examples/blob/master/nextjs-v14 worked and my project didn't I removed files one by one, making smaller and smaller changes, I though problem was in bun, in node modules cache, in next.js versions difference, until eventually I was left with two identical projects (I even changed .tsx to .js) but in one directory it worked and it another it didn't
Turns out, if I add spaces to the path where project is and where I'm running it, it will fail to compile throwing this long error:
Reproduction
https://github.com/module-federation/module-federation-examples/blob/master/nextjs-v14
Used Package Manager
npm
System Info
Validations