Repository navigation
Import of headless.conf.js breaks in Windows due to incorrect pathname #866
Description
Activity
Thanks for the report.
While I'd typically recommend using WSL2, this should be an easy fix, we just need to make path resolution in
withHeadstartWPConfigcross-platform and alongside that include windows to run our test builds in CI.Did you fix it? I still have the same error
- added a commit that references this issue
on Apr 25, 2025 This has been fixed (but not yet released). A separate issue on windows has been opened #902 which seems to be a Next.js issue.
Describe the bug
Using NextJS 14.2 in Windows dev environment. Throws errors that it can't import the config file, and the pathname in the errors is missing the slashes:
c:somethingSomethingDirheadless.config.jsI confirmed that merging the configs with withHeadlessConfig() the output is ok, so loading the config in next.config.js is working fine, it's the loading in the package that breaks.
Steps to Reproduce
npm run devin WindowsScreenshots, screen recording, code snippet
No response
Environment information
NextJS 14.2.13
Windows
Nodejs 20
WordPress information
No response
Code of Conduct