-
-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with typings with later versions of hast
#750
Labels
📦 area/deps
This affects dependencies
👀 no/external
This makes more sense somewhere else
👎 phase/no
Post cannot or will not be acted on
Comments
github-actions
bot
added
👋 phase/new
Post is being triaged automatically
🤞 phase/open
Post is being triaged manually
and removed
👋 phase/new
Post is being triaged automatically
labels
Jul 11, 2023
This is an upstream issue that’s being worked on. See DefinitelyTyped/DefinitelyTyped#65789 (comment) for details and a workaround. |
This comment has been minimized.
This comment has been minimized.
remcohaszing
added
📦 area/deps
This affects dependencies
👀 no/external
This makes more sense somewhere else
👎 phase/no
Post cannot or will not be acted on
and removed
🤞 phase/open
Post is being triaged manually
labels
Jul 11, 2023
External as Remco mentions, see DefinitelyTyped/DefinitelyTyped#66029. |
wooorm
added
👀 no/external
This makes more sense somewhere else
and removed
👀 no/external
This makes more sense somewhere else
labels
Jul 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
📦 area/deps
This affects dependencies
👀 no/external
This makes more sense somewhere else
👎 phase/no
Post cannot or will not be acted on
Initial checklist
Affected packages and versions
react-markdown
Link to runnable example
No response
Steps to reproduce
Install
react-markdown
and run typescript with--skipLibCheck=false
Expected behavior
Types are happy and the library has 0 typescript errors
Actual behavior
Looks like there's some type incompatibility with later packages that have been released. This is blocking our pipeline and E2e tests for Backstage. We've had a suggestion that a potential fix is to bring in
@types/unist@<3.0.0
, maybe that needs implementing here or should we open an issue over there?backstage/backstage#18643
Runtime
No response
Package manager
No response
OS
No response
Build and bundle tools
No response
The text was updated successfully, but these errors were encountered: