isomorphic-dompurify 1.0.0 → 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -4,7 +4,7 @@
4
4
  [![Bundlephobia Minified Size](https://badgen.net/bundlephobia/min/isomorphic-dompurify)](https://bundlephobia.com/result?p=isomorphic-dompurify)
5
5
 
6
6
  The library makes it possible to seamlessly use [DOMPurify](https://github.com/cure53/DOMPurify) on server and client in the same way.
7
- It does nothing by itself except providing an isomorthic/universal wrapper around DOMPurify, so all credits go to DOMPurify authors and contributors.
7
+ It does nothing by itself except providing an isomorphic/universal wrapper around DOMPurify, so all credits go to DOMPurify authors and contributors.
8
8
 
9
9
  > 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.
10
10
  - [DOMPurify Demo](https://cure53.de/purify)
@@ -12,9 +12,9 @@ It does nothing by itself except providing an isomorthic/universal wrapper aroun
12
12
 
13
13
  ## Motivation
14
14
 
15
- 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 server is not the same as on client.
15
+ 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.
16
16
 
17
- This project was born with the idea of encapsulating DOMPurify initilization details and providing an easy way to import the library on both, server and client, for example in Next.js apps.
17
+ 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.
18
18
 
19
19
  It was inspired by [Isomorphic Unfetch](https://github.com/developit/unfetch/tree/master/packages/isomorphic-unfetch).
20
20
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "isomorphic-dompurify",
3
- "version": "1.0.0",
3
+ "version": "1.2.0",
4
4
  "description": "Makes it possible to use DOMPurify on server and client in the same way.",
5
5
  "keywords": [
6
6
  "security",
@@ -29,14 +29,14 @@
29
29
  "repository": "kkomelin/isomorphic-dompurify",
30
30
  "browser": "browser.js",
31
31
  "main": "index.js",
32
+ "types": "index.d.ts",
32
33
  "dependencies": {
33
- "@types/dompurify": "^2.4.0",
34
- "dompurify": "^3.0.0",
34
+ "@types/dompurify": "^3.0.0",
35
+ "dompurify": "^3.0.1",
35
36
  "jsdom": "^21.1.0"
36
37
  },
37
- "types": "index.d.ts",
38
38
  "devDependencies": {
39
- "jest": "^29.4.2",
40
- "terser": "^5.16.3"
39
+ "jest": "^29.5.0",
40
+ "terser": "^5.16.5"
41
41
  }
42
42
  }