parse5
                                
                                
                                
                                    parse5 copied to clipboard
                            
                            
                            
                        HTML parsing/serialization toolset for Node.js. WHATWG HTML Living Standard (aka HTML5)-compliant.
Not sure if this PR should be merged at this time. The `` element is tested in `html5lib-tests`, but the PR for the spec hasn't been merged yet (https://github.com/whatwg/html/pull/7320). It...
This is prep work for me turning the non-null-assertion rule on to `error`. Summary: * eslint:recommended wasn't enabled for `*.ts` so i have enabled it * unicorn wasn't used at...
Depends on #454 , draft until then. Fixes #377
We should set `@typescript-eslint/explicit-member-accessibility` to `error`. This will require that all members now have accessibility modifiers (e.g. `public`). Should be an easy one, though it will probably uncover a lot...
AST Explorer link: https://astexplorer.net/#/gist/25e9a360157ab2e56a7bf14ac22daa5b/196c723e25cf99ec923c3ce0be36664817b264d2 ```xml ``` Given the SVG element above, the AST produces an svg element node whose `attrs` array has a `{ name: 'viewBox', value: '0 0 100...
We should enable the rule to disallow non-null assertions: ```ts foo!.bar!.baz; ``` from what i remember, we have quite a lot of these scattered around because of the whole "bootstrap"...
The [Attribute interface](https://github.com/inikulin/parse5/blob/master/packages/parse5/docs/tree-adapter/default/attribute.md) has four properties named `name`, `namespace`, `prefix` and `value`. Three of these share their names with the [Attr interface](https://dom.spec.whatwg.org/#attr) of the DOM. However, there `namespace` is named...
I don't see a link in the README.md that lets people get to the docs that cover the API for this package... can that be added?
Hello I can't use the HTML rewriting with a Promise I do have an error: Error [ERR_STREAM_PUSH_AFTER_EOF]: stream.push() after EOF This is my code : ``` const RewritingStream = require('parse5-html-rewriting-stream');...
The `| Object` in each of the main types is both correct and well intentioned, but it renders the type useless to the type checker, as `foo | Object` simplifies...