dify - 💡(How to fix) Fix Local Cloud edition dev loads production analytics scripts and shows a Script error overlay [1 pull requests]

Problem

When the web app is started locally with NEXT_PUBLIC_EDITION=CLOUD, the Cloud-only analytics scripts are treated as eligible to render even though the app is running in a local development environment.

That makes the local /apps page attempt to load production third-party analytics infrastructure, including the CookieYes banner script. The production CookieYes site key is registered for the production website, not localhost, so the script throws at runtime.

Observed behavior

• The browser console reports an uncaught CookieYes error saying the website URL has changed and the registered site URL should be updated.
• The dev overlay surfaces this as an unhandled Script error.
• The overlay points at vinext's dev error overlay, but the underlying error is from the third-party CookieYes script.

Expected behavior

Local development should be able to run with NEXT_PUBLIC_EDITION=CLOUD to exercise Cloud product behavior without loading production analytics or consent-banner scripts that are tied to production domains.

Notes

This is a problem report only. The important boundary is that product edition (CLOUD) and production runtime are not the same condition for loading external analytics scripts.