Please open an issue in nextjs

I also added it to vercel/next.js#29752

@getTobiasNielsen Can you provide steps to reproduce?

Yep, I can switch between two different branches, and it's on the build in one, but not in the other.

As previously stated, I just changed some html into components. After trying to build that commit, I have to clean the cache, or I get the error in question.

The offer for access still stands.

Something changes more except HTML? Maybe package.json? Maybe you have hooks on install deps on switching branches

Something changes more except HTML? Maybe package.json? Maybe you have hooks on install deps on switching branches

I wish it so.

Here's everything that's being done.

I tried re-adding the api folder and hello.ts, but didn't change anything.

Thanks for feedback

We're about to decide to publish the repo, just waiting for peoples consent. Should give you more to work with.

I specifically deleted the client-production cache of webpack, to clear the problem

https://github.com/Publica-Fides/publica-fides-webapp

There are two branches, switching between test4 and test5 and building them with npx next build should introduce the error.

Let me know if you are able to.

I still get this error when building my Next.js app in GitHub actions. 🤔 Although when I build the app in my local machine, no issues, even when deleting my node_modules folder and yarn.lock. Do you guys have an idea?

@dominicarrojado Maybe CI cache?

@dominicarrojado Maybe CI cache?

Yes, you're right. That was the issue and apparently GitHub doesn't allow manual purge so I disabled the caching first and it finally build successfully. Thanks!