fix(nextjs-mf): Try CSP-safe method for getting globalThis first

[mitchellrj]

Description

Where unsafe-eval is not permitted in a Content Security Policy, trying the Function approach first then falling back causes unnecessary CSP Reports and errors to be logged by the browser. This approach uses globalThis by default, then attempts to catch the Webpack rewriting of it.

Related Issue

#3772

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated the documentation.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7fde21f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for module-federation-docs ready!

Name	Link
🔨 Latest commit	7fde21f
🔍 Latest deploy log	https://app.netlify.com/projects/module-federation-docs/deploys/6846abd496ea740008a342eb
😎 Deploy Preview	https://deploy-preview-3776--module-federation-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ScriptedAlchemy]

@mitchellrj run pnpm changeset add

[ScriptedAlchemy]

@mitchellrj bump

[mitchellrj]

@ScriptedAlchemy want me to bring up to date with main again?

[mitchellrj]

There's still an issue with the type of __webpack_require__.g not being defined. I'm not so familiar with how to fix that.

[ScriptedAlchemy]

Okay does latest PR seem to work? address previous comments?

[mitchellrj]

The tests are passing.

I tried building locally to test e2e, but that is where I run into the __webpack_require__.g issue previously described.

I think that it is fixed in my changes to webpack/module.d.ts but the CONTRIBUTORS file doesn't give me instructions to get a build working locally to test it myself, so I'm not sure if I'm doing it right. Sorry, I'm quite new to this.

[ScriptedAlchemy]

Oh its just type errors. We can tsignore it if its not behaving. As long as not real error that crash app