Jack van der Bilt
Jack van der Bilt
Any progress on this? Running on a top-of-the-line machine and it still takes 3 to 4 seconds...
I'm parsing a superset of HTML; see below for snippet. The error is thrown by the `util.js` `isName` function, which is used by the parser. I do not see any...
For now I worked around this by modifying my node_modules, but that is not maintainable solution in the long run. ```js const nameStartChar = ':A-Za-z_\\u00C0-\\u00D6\\u00D8-\\u00F6\\u00F8-\\u02FF\\u0370-\\u037D\\u037F-\\u1FFF\\u200C-\\u200D\\u2070-\\u218F\\u2C00-\\u2FEF\\u3001-\\uD7FF\\uF900-\\uFDCF\\uFDF0-\\uFFFD@\$'; // Note the additional @...
Yes; ```js const config = { allowBooleanAttributes: true, alwaysCreateTextNode: true, preserveOrder: true, parseAttributeValue: false, htmlEntities: false, isArray: true, attributeNamePrefix: '', ignoreAttributes: false, unpairedTags: ["hr", "br", "link", "meta"], stopNodes : [...
Sorry, I misunderstood your question; this is what I pass to the second parameter in the parse method: `{ allowBooleanAttributes: true }`
Also having this issue
+1 waiting for this feature
Could you add support for `// comment` style comments? In one of my projects we use a different flavor of css that uses these comments instead. We had a similar...
Opened a PR to contribute: #43
Can't you just swap the edge browser with chrome? As in, literally swap the binary files and change the icon for every shortcut? Or maybe symlink some shit? Idk man...