Closed Methuselah96 closed 1 year ago
You’re right, this should be an explicit dependency. Would you like to add a PR for this?
Hi! This was marked as ready to be worked on! Note that while this is ready to be worked on, nothing is said about priority: it may take a while for this to be solved.
Is this something you can and want to work on?
Team: please use the area/*
(to describe the scope of the change), platform/*
(if this is related to a specific one), and semver/*
and type/*
labels to annotate this. If this is first-timers friendly, add good first issue
and if this could use help, add help wanted
.
Hi! This was marked as ready to be worked on! Note that while this is ready to be worked on, nothing is said about priority: it may take a while for this to be solved.
Is this something you can and want to work on?
Team: please use the area/*
(to describe the scope of the change), platform/*
(if this is related to a specific one), and semver/*
and type/*
labels to annotate this. If this is first-timers friendly, add good first issue
and if this could use help, add help wanted
.
Initial checklist
Affected packages and versions
hast-util-raw@8.0.0 and hast-util-raw@9.0.0
Looks like the reference to
@types/unist
was introduced in https://github.com/syntax-tree/hast-util-raw/pull/17.Link to runnable example
No response
Steps to reproduce
hast-util-raw
with a strict package manager like Yarn PnP andskipLibCheck
set tofalse
.Expected behavior
No type errors.
Actual behavior
Type error:
Affected runtime and version
N/A
Affected package manager and version
No response
Affected OS and version
No response
Build and bundle tools
No response