Gathering detailed insights and metrics for unist-util-visit-parents
Gathering detailed insights and metrics for unist-util-visit-parents
Gathering detailed insights and metrics for unist-util-visit-parents
Gathering detailed insights and metrics for unist-util-visit-parents
utility to recursively walk over unist nodes, with ancestral information
npm install unist-util-visit-parents
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
67 Stars
136 Commits
7 Forks
9 Watching
1 Branches
12 Contributors
Updated on 15 Nov 2024
JavaScript (83.39%)
TypeScript (16.61%)
Cumulative downloads
Total Downloads
Last day
-7.4%
2,837,876
Compared to previous day
Last week
1.6%
16,247,480
Compared to previous week
Last month
6.4%
69,126,404
Compared to previous month
Last year
31.1%
742,231,857
Compared to previous year
unist utility to walk the tree with a stack of parents.
This is a very important utility for working with unist as it lets you walk the tree.
You can use this utility when you want to walk the tree and want to know about
every parent of each node.
You can use unist-util-visit
if you don’t care about the
entire stack of parents.
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install unist-util-visit-parents
In Deno with esm.sh
:
1import {visitParents} from 'https://esm.sh/unist-util-visit-parents@6'
In browsers with esm.sh
:
1<script type="module"> 2 import {visitParents} from 'https://esm.sh/unist-util-visit-parents@6?bundle' 3</script>
1import {visitParents} from 'unist-util-visit-parents' 2import {fromMarkdown} from 'mdast-util-from-markdown' 3 4const tree = fromMarkdown('Some *emphasis*, **strong**, and `code`.') 5 6visitParents(tree, 'strong', function (node, ancestors) { 7 console.log(node.type, ancestors.map(ancestor => ancestor.type)) 8})
Yields:
1strong ['root', 'paragraph']
This package exports the identifiers CONTINUE
,
EXIT
, SKIP
, and visitParents
.
There is no default export.
visitParents(tree[, test], visitor[, reverse])
Visit nodes, with ancestral information.
This algorithm performs depth-first tree traversal
in preorder (NLR) or if reverse
is given, in reverse preorder
(NRL).
You can choose for which nodes visitor
is called by passing a test
.
For complex tests, you should test yourself in visitor
, as it will be
faster and will have improved type information.
Walking the tree is an intensive task.
Make use of the return values of the visitor when possible.
Instead of walking a tree multiple times, walk it once, use
unist-util-is
to check if a node matches, and then perform
different operations.
You can change the tree.
See Visitor
for more info.
tree
(Node
)
— tree to traversetest
(Test
, optional)
— unist-util-is
-compatible testvisitor
(Visitor
)
— handle each nodereverse
(boolean
, default: false
)
— traverse in reverse preorder (NRL) instead of the default preorder (NLR)Nothing (undefined
).
CONTINUE
Continue traversing as normal (true
).
EXIT
Stop traversing immediately (false
).
SKIP
Do not traverse this node’s children ('skip'
).
Action
Union of the action types (TypeScript type).
1type Action = typeof CONTINUE | typeof EXIT | typeof SKIP
ActionTuple
List with one or two values, the first an action, the second an index (TypeScript type).
1type ActionTuple = [ 2 (Action | null | undefined | void)?, 3 (Index | null | undefined)? 4]
BuildVisitor
Build a typed Visitor
function from a tree and a test (TypeScript type).
It will infer which values are passed as node
and which as parents
.
Index
Move to the sibling at index
next (after node itself is completely
traversed) (TypeScript type).
Useful if mutating the tree, such as removing the node the visitor is currently
on, or any of its previous siblings.
Results less than 0
or greater than or equal to children.length
stop
traversing the parent.
1type Index = number
Test
unist-util-is
compatible test (TypeScript type).
Visitor
Handle a node (matching test
, if given) (TypeScript type).
Visitors are free to transform node
.
They can also transform the parent of node (the last of ancestors
).
Replacing node
itself, if SKIP
is not returned, still causes its
descendants to be walked (which is a bug).
When adding or removing previous siblings of node
(or next siblings, in
case of reverse), the Visitor
should return a new Index
to specify the
sibling to traverse after node
is traversed.
Adding or removing next siblings of node
(or previous siblings, in case
of reverse) is handled as expected without needing to return a new Index
.
Removing the children property of an ancestor still results in them being traversed.
node
(Node
)
— found nodeparents
(Array<Node>
)
— ancestors of node
What to do next.
An Index
is treated as a tuple of [CONTINUE, Index]
.
An Action
is treated as a tuple of [Action]
.
Passing a tuple back only makes sense if the Action
is SKIP
.
When the Action
is EXIT
, that action can be returned.
When the Action
is CONTINUE
, Index
can be returned.
VisitorResult
Any value that can be returned from a visitor (TypeScript type).
1type VisitorResult = 2 | Action 3 | ActionTuple 4 | Index 5 | null 6 | undefined 7 | void
This package is fully typed with TypeScript.
It exports the additional types Action
,
ActionTuple
, BuildVisitor
,
Index
, Test
, Visitor
, and
VisitorResult
.
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,
unist-util-visit-parents@^6
, compatible with Node.js 16.
unist-util-visit
— walk the tree with one parentunist-util-filter
— create a new tree with all nodes that pass a testunist-util-map
— create a new tree with all nodes mapped by a given functionunist-util-flatmap
— create a new tree by mapping (to an array) with the given functionunist-util-remove
— remove nodes from a tree that pass a testunist-util-select
— select nodes with CSS-like selectorsSee 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 dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
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
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