The library makes it possible to seamlessly use DOMPurify on server and client in the same way. It does nothing by itself except providing an isomorphic/universal wrapper around DOMPurify, so all credits go to DOMPurify authors and contributors.
DOMPurify - a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMPurify works with a secure default, but offers a lot of configurability and hooks.
DOMPurify needs a DOM tree to base on, which is not available in Node by default. To work on the server side, we need a fake DOM to be created and supplied to DOMPurify. It means that DOMPurify initialization logic on the server is not the same as on the client.
This project was born with the idea of encapsulating DOMPurify initialization details and providing an easy way to import the library on both, server and client, for example in Next.js apps.
It was inspired by Isomorphic Unfetch.
| isomorphic-dompurify | Node.js | Environment |
|---|---|---|
<=0.19.0 |
>=12 |
Server |
>=0.20.0 |
>=14 |
Server |
>=1.4.0 |
>=16 |
Server |
>=1.10.0 |
>=18 |
Server |
$ npm i isomorphic-dompurify
Please note that DOMPurify library doesn't follow Semantic Versioning, so we have to release every change as a minor version because we cannot be 100% sure whether new features are added to patch DOMPurify releases or not.
Import:
import DOMPurify from "isomorphic-dompurify";Importing the entire module for the client/browser version is recommended.
Sanitize:
const clean = DOMPurify.sanitize(dirtyString);or with config:
const clean = DOMPurify.sanitize(dirtyString, { USE_PROFILES: { html: true } });- Next.js and Remix are mistakenly trying to use the
browserentry point on server, which causes theWindow is not definedissue. #228 #214 vercel/next.js#58142 - Can't resolve 'canvas' on Next.js serverless app
DOMPurify - Apache 2.0 or MPL 2.0 © 2015 Mario Heiderich
Isomorphic DOMPurify - MIT License © 2020 Konstantin Komelin and contributors