Repository navigation
Fix DOMPurify crash in SSR environment - #151
Conversation
Replaces direct DOMPurify usage with a safe wrapper that handles server-side execution and potential factory function exports. This prevents TypeError during rendering. Co-authored-by: egoing <303822+egoing@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Introduced
safeSanitizeutility insrc/utils/sanitize.tsto handle DOMPurify initialization correctly across environments (Client vs Server).Replaced direct
DOMPurify.sanitizecalls withsafeSanitizein:src/components/common/ConfirmDialog/index.tsxsrc/components/common/BlockNoteEditor/EditorLoadingErrorFallback.tsxsrc/components/common/ContentListMessage/index.tsxsrc/components/layout/bottom/agreement/docDialog.tsxsrc/components/Chat/Root/Conversation/index.tsxThis prevents the application from crashing with
TypeError: ... is not a functionduring rendering when DOMPurify is imported as a factory function on the server.PR created automatically by Jules for task 7914228733767260048 started by @egoing