nextjs - 💡(How to fix) Fix Firefox shows forward-logs-shared.ts as source in console for all next logs [8 comments, 6 participants]

TL;DR

The issue with incorrect source logging in Firefox can be addressed by investigating the differences in how Next.js handles source mapping between Chrome and Firefox.

Guidance

• Verify that the issue is specific to Firefox by testing with other browsers to confirm if the problem is browser-specific.
• Check the Next.js documentation and source code for any known issues or differences in how source maps are handled between browsers.
• Investigate the forward-logs-shared.ts file to understand why it's being reported as the source instead of page.tsx.
• Review the browser's DevTools settings and configuration to ensure that source maps are enabled and properly configured.

Example

No specific code example can be provided without further investigation, but checking the Next.js configuration and source maps settings might look something like this:

// next.config.js
module.exports = {
  //... other configurations ...
  compilerOptions: {
    //... other options ...
    sourceMap: true, // Ensure source maps are enabled
  },
}

Notes

The issue seems to be related to how Next.js handles source mapping in Firefox, but without more information or a deeper dive into the code, it's difficult to provide a definitive solution. The fact that Chrome logs the correct source suggests a potential browser-specific issue.

Recommendation

Apply workaround: Investigate and adjust Next.js source map configurations and settings to ensure compatibility with Firefox, as the issue seems to be browser-specific and not a version-related problem with Next.js itself.