Tons of this 311.js error

[charleslcso]

Hello

cal.com seems to run: I can log in, I can load Event Types. But eventually it will crash, and console output is full of this:

@calcom/web:dx: Error: Cannot find module './331.js'
@calcom/web:dx: Require stack:
@calcom/web:dx: - /opt/cal.com/apps/web/.next/server/webpack-runtime.js
@calcom/web:dx: - /opt/cal.com/apps/web/.next/server/pages/_document.js
@calcom/web:dx: - /opt/cal.com/node_modules/next/dist/server/require.js
@calcom/web:dx: - /opt/cal.com/node_modules/next/dist/server/load-components.js
...
@calcom/web:dx: code: 'MODULE_NOT_FOUND',
@calcom/web:dx: requireStack: [
@calcom/web:dx: '/opt/cal.com/apps/web/.next/server/webpack-runtime.js',
@calcom/web:dx: '/opt/cal.com/apps/web/.next/server/pages/_document.js',
...
@calcom/web:dx: ]
@calcom/web:dx: }

What am I doing wrong or missed?

[dosubot[bot]]

The error you're encountering, "Cannot find module './331.js'," suggests that there is a missing module or a misconfiguration in your setup. Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Check for Missing Files: Ensure that the 331.js file is present in the expected directory. If it's missing, you might need to restore it from a backup or check if it was accidentally deleted.

2. Verify Build Process: Sometimes, build processes might not include all necessary files. Try running a clean build of your project to ensure all files are correctly generated and included.

3. Inspect Webpack Configuration: Since the error is related to module resolution, check your Webpack configuration for any custom settings that might affect how modules are resolved. Ensure that there are no incorrect path aliases or missing configurations.

4. Check for Recent Changes: If this issue started occurring after a recent change, review the changes to see if anything might have affected module imports or file paths.

5. Dependencies and Updates: Ensure all your dependencies are up to date. Sometimes, issues can arise from outdated packages or incompatible versions.

6. Module Resolution Configuration: Review your tsconfig.json or any other configuration files related to module resolution to ensure they are correctly set up. For example, the tsconfig in the cal.com project uses custom path mappings that need to be correctly configured ^[1][2].

If none of these steps resolve the issue, you might need to delve deeper into the specific setup and configuration of your environment to identify any discrepancies.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[charleslcso]

The error you're encountering, "Cannot find module './331.js'," suggests that there is a missing module or a misconfiguration in your setup. Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Check for Missing Files: Ensure that the 331.js file is present in the expected directory. If it's missing, you might need to restore it from a backup or check if it was accidentally deleted.
2. Verify Build Process: Sometimes, build processes might not include all necessary files. Try running a clean build of your project to ensure all files are correctly generated and included.
3. Inspect Webpack Configuration: Since the error is related to module resolution, check your Webpack configuration for any custom settings that might affect how modules are resolved. Ensure that there are no incorrect path aliases or missing configurations.
4. Check for Recent Changes: If this issue started occurring after a recent change, review the changes to see if anything might have affected module imports or file paths.
5. Dependencies and Updates: Ensure all your dependencies are up to date. Sometimes, issues can arise from outdated packages or incompatible versions.
6. Module Resolution Configuration: Review your tsconfig.json or any other configuration files related to module resolution to ensure they are correctly set up. For example, the tsconfig in the cal.com project uses custom path mappings that need to be correctly configured [1][2].

If none of these steps resolve the issue, you might need to delve deeper into the specific setup and configuration of your environment to identify any discrepancies.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

As I'm new to cal.com, I have not done anything silly by customising it... no customisation. Just change .env. Nothing's been removed, no other files are revised, haven't touched Webpack, nothing's added to any directories.

Would some version of yarn cause issue? I didn't have the correct version of yarn, and it couldn't load yarn dx.

I'll create a new LXC and start all over again.

[charleslcso]

Ok, I attempted another clean install by using a new LXC.

I can yarn build now. It succeed.

The reason why it failed on the previous LXC could be: a bad version of yarn was installed first, then even though it was removed and THE one is installed, something still got messed up and that's why it failed every time.