Module not Found error returned when trying to run the project

[Thiagomn1]

Issue Summary

After perfoming all the setup steps and trying to run the project locally by running yarn dev to start the server, the console returns the following error.

Steps to Reproduce

1. Set up a new local instance of the project
2. Start the development server with yarn dev

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

Technical details

• Node Version: 16.15.0
• Set up done in windows

[PeerRich]

can you try yarn clean then yarn ?

[Thiagomn1]

Ran the clean and built again but still returns the same error when starting the dev server. It complains about error - Cannot read properties of null (reading '1')

[PeerRich]

very odd

[PeerRich]

can you try executing this on vercel? so we know its not a code bug but maybe a local bug on your machine

[mocherfaoui]

I have the same problem, and I think these errors started to show after a change to next.config.js at some point

[Sagargajare]

@PeerRich Getting same error on my local system

[PeerRich]

we're investigating.

can't reproduce this on my end tho

[PeerRich]

can y'all try yarn dx? with docker running

[Sagargajare]

with docker I got this issue DATABASE_URL missing in schema.prisma:6 #2396

[alishaz-polymath]

@Sagargajare Please take a look at this

[alishaz-polymath]

I can confirm that this is currently an error for the windows systems, and we're working on a solution. The issue is definitely related to the changes in the config made in #3986 PR. I would recommend that you try reverting the changes from the PR by re-adding the apps/web/pages/api/app-store/[...static].ts file listed as deleted in the PR, and revert the changes in the apps/web/next.config.js file as an interim solution. We are actively working on getting this resolved soon for windows machines as well.
🙏

[ameyer117]

Stil broken to this day. Not supporting Windows is pathetic.

[alishaz-polymath]

Windows support exists, there's simply a workaround for it for now, until a robust solution is confirmed. 🙏

[alishaz-polymath]

This has now been resolved in #5602 #5636
🙏
Thank you all for your patience

[ameyer117]

🙌