abvanton200 / critical-css-parser Goto Github PK

Any tips on configuring linting rules in this bad boy? dropcss.cs.js throws error around this line:
'var TAG_OPEN = 1;'

error:

if (VOIDS.has(tag) || m2[1] == "/>")

TypeError: Cannot read property '1' of null
at next (.....\node_modules\dropcss\dist\dropcss.cjs.js:70:28)
at tokenize (.....\node_modules\dropcss\dist\dropcss.cjs.js:87:3)
at export_parse .....\node_modules\dropcss\dist\dropcss.cjs.js:195:15)
at dropcss (.....\node_modules\dropcss\dist\dropcss.cjs.js:969:10)
at n (.....\node_modules\critical-css-parser\dist\index.modern.js:1:2055)
at module.exports (.....\node_modules\critical-css-parser\dist\index.modern.js:1:3197)
at async module.exports (.....\node_modules\critical-css-inliner\dist\index.modern.js:1:512)
at async .\critical_css_inliner.js:5:3

'critical_css_inliner.js is script it's running from, same error with critical-css-parser and critical_css_inliner

@ABVanton200

#card {
  position: absolute;
  top: 1000%;
}

this will probably remove this #card element, then drop its CSS and on the real page it will now (wrongly) appear above the fold.

i can't think of a solution to this. but you may want to mention that stuff like this can happen if elements are moved below the fold by css only.