Skip to content

build(package): upgrade html-dom-parser@0.3.0 and devDependencies #159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jun 2, 2020
Merged

build(package): upgrade html-dom-parser@0.3.0 and devDependencies #159

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
cc5b3e3
build(package): downgrade standard-version@6
remarkablemark Jun 2, 2020
5e104db
build(package): upgrade devDependencies
remarkablemark Jun 2, 2020
f189246
build(package): update rollup plugins in devDependencies
remarkablemark Jun 2, 2020
d30bfdc
feat(package): upgrade html-dom-parser@0.3.0
remarkablemark Jun 2, 2020
606d959
docs(readme): update FAQ with section on invalid HTML
remarkablemark Jun 2, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ The first argument is an object with the same output as [htmlparser2](https://gi

```js
parse('<br>', {
replace: function(domNode) {
replace: function (domNode) {
console.dir(domNode, { depth: null });
}
});
Expand Down Expand Up @@ -250,6 +250,16 @@ Check if your arguments are valid. Also, see ["Does this library sanitize invali

Yes, this library supports server-side rendering on Node.js. See [demo](https://repl.it/@remarkablemark/html-react-parser-SSR).

#### Why are my elements nested incorrectly?

Make sure your [HTML markup is valid](https://validator.w3.org/). The HTML to DOM parsing will be affected if you're using self-closing syntax (`/>`) on non-void elements:

```js
parse('<div /><div />'); // returns single element instead of array of elements
```

See [#158](https://github.com/remarkablemark/html-react-parser/issues/158).

## Benchmarks

```sh
Expand Down
16 changes: 8 additions & 8 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,32 +33,32 @@
],
"dependencies": {
"@types/domhandler": "2.4.1",
"html-dom-parser": "0.2.3",
"html-dom-parser": "0.3.0",
"react-property": "1.0.1",
"style-to-object": "0.3.0"
},
"devDependencies": {
"@commitlint/cli": "^8.3.5",
"@commitlint/config-conventional": "^8.3.4",
"@rollup/plugin-commonjs": "^12.0.0",
"@rollup/plugin-node-resolve": "^8.0.0",
"@types/react": "^16.9.35",
"benchmark": "^2.1.4",
"dtslint": "^3.6.4",
"dtslint": "^3.6.10",
"eslint": "^7.1.0",
"eslint-plugin-prettier": "^3.1.3",
"husky": "^4.2.5",
"lint-staged": "^10.2.6",
"lint-staged": "^10.2.7",
"mocha": "^7.2.0",
"nyc": "^15.0.1",
"nyc": "^15.1.0",
"preact": "^10.4.4",
"prettier": "^2.0.5",
"react": "^16",
"react-dom": "^16",
"rimraf": "^3.0.2",
"rollup": "^1.32.1",
"rollup-plugin-commonjs": "^10.1.0",
"rollup-plugin-node-resolve": "^5.2.0",
"rollup": "^2.12.1",
"rollup-plugin-uglify": "^6.0.4",
"standard-version": "^6",
"standard-version": "^5",
"typescript": "^3.9.3"
},
"peerDependencies": {
Expand Down
4 changes: 2 additions & 2 deletions rollup.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
import commonjs from 'rollup-plugin-commonjs';
import resolve from 'rollup-plugin-node-resolve';
import commonjs from '@rollup/plugin-commonjs';
import resolve from '@rollup/plugin-node-resolve';
import { uglify } from 'rollup-plugin-uglify';

/**
Expand Down