Gathering detailed insights and metrics for hast-util-raw
Gathering detailed insights and metrics for hast-util-raw
Gathering detailed insights and metrics for hast-util-raw
Gathering detailed insights and metrics for hast-util-raw
npm install hast-util-raw
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
11 Stars
173 Commits
4 Forks
10 Watching
1 Branches
13 Contributors
Updated on 14 Nov 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-1.3%
669,843
Compared to previous day
Last week
2.8%
3,466,569
Compared to previous week
Last month
11.7%
14,591,386
Compared to previous month
Last year
-19.4%
172,385,616
Compared to previous year
13
hast utility to parse the tree and semistandard raw
nodes (strings of
HTML) again, keeping positional info okay.
This package is a utility to parse a document again.
It passes each node and embedded raw HTML through an HTML parser
(parse5
), to recreate a tree exactly as how a browser would parse
it, while keeping the original data and positional info intact.
This utility is particularly useful when coming from markdown and wanting to
support HTML embedded inside that markdown (which requires passing
allowDangerousHtml: true
to mdast-util-to-hast
).
Markdown dictates how, say, a list item or emphasis can be parsed.
We can use that to turn the markdown syntax tree into an HTML syntax tree.
But markdown also dictates that things that look like HTML, are passed through
untouched, even when it just looks like XML but doesn’t really make sense, so we
can’t normally use these strings of “HTML” to create an HTML syntax tree.
This utility can.
It can be used to take those strings of HTML and include them into the syntax
tree as actual nodes.
If your final result is HTML and you trust content, then “strings” are fine
(you can pass allowDangerousHtml: true
to hast-util-to-html
, which passes
HTML through untouched).
But there are two main cases where a proper syntax tree is preferred:
The plugin rehype-raw
wraps this utility at a higher-level
(easier) abstraction.
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install hast-util-raw
In Deno with esm.sh
:
1import {raw} from 'https://esm.sh/hast-util-raw@9'
In browsers with esm.sh
:
1<script type="module"> 2 import {raw} from 'https://esm.sh/hast-util-raw@9?bundle' 3</script>
1import {h} from 'hastscript' 2import {raw} from 'hast-util-raw' 3 4const tree = h('div', [h('h1', ['Foo ', h('h2', 'Bar'), ' Baz'])]) 5 6const reformatted = raw(tree) 7 8console.log(reformatted)
Yields:
1{ type: 'element', 2 tagName: 'div', 3 properties: {}, 4 children: 5 [ { type: 'element', 6 tagName: 'h1', 7 properties: {}, 8 children: [Object] }, 9 { type: 'element', 10 tagName: 'h2', 11 properties: {}, 12 children: [Object] }, 13 { type: 'text', value: ' Baz' } ] }
Options
Configuration.
file?
(VFile | null | undefined
)
— corresponding virtual file representing the input document (optional)
passThrough?
(Array<string> | null | undefined
)
List of custom hast node types to pass through (as in, keep) (optional).
If the passed through nodes have children, those children are expected to be hast again and will be handled.
tagfilter?
(boolean | null | undefined
)
Whether to disallow irregular tags in raw
nodes according to GFM
tagfilter
(default: false
).
This affects the following tags, grouped by their kind:
RAWTEXT
: iframe
, noembed
, noframes
, style
, xmp
RCDATA
: textarea
, title
SCRIPT_DATA
: script
PLAINTEXT
: plaintext
When you know that you do not want authors to write these tags,
you can enable this option to prevent their use from running amok.raw(tree, options)
Pass a hast tree through an HTML parser, which will fix nesting, and turn raw nodes into actual nodes.
tree
(Root | RootContent
)
— original hast tree to transformoptions?
(Options | null | undefined
)
— configuration (optional)Parsed again tree (Root | RootContent
).
This package is fully typed with TypeScript.
It exports the additional type Options
.
The Raw
node type is registered by and exposed from
mdast-util-to-hast
.
Projects maintained by the unified collective are compatible with maintained versions of Node.js.
When we cut a new major release, we drop support for unmaintained versions of
Node.
This means we try to keep the current release line, hast-util-raw@^9
,
compatible with Node.js 16.
Use of hast-util-raw
can open you up to a cross-site scripting (XSS)
attack as raw
nodes are unsafe.
The following example shows how a raw node is used to inject a script that runs
when loaded in a browser.
1raw(u('root', [u('raw', '<script>alert(1)</script>')]))
Yields:
1<script>alert(1)</script>
Either do not use this utility in combination with user input, or use
hast-util-santize
.
mdast-util-to-hast
— transform mdast to hastrehype-raw
— rehype pluginSee contributing.md
in syntax-tree/.github
for
ways to get started.
See support.md
for ways to get help.
This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
security policy file detected
Details
Reason
9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Reason
Found 1/30 approved changesets -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More