Closed rognierbenoit closed 1 year ago
Hi! This was closed. Team: If this was fixed, please add phase/solved
. Otherwise, please add one of the no/*
labels.
The solution is to comment the line out ?
No, that is not a solution. Why would you use TypeScript but not want types? That doesn’t make sense.
The solution is either:
Node
from the correct place here"skipLibCheck": true,
in your TS config fileThat’s what they’re reporting. micromark-extension-mdx-expression
imports Node
from the wrong place. This is fixed in https://github.com/micromark/micromark-extension-mdx-expression/commit/350fe0bf8d0fae9cf1d619585af87905b692aa5d#diff-862b7cc1d1766f73cb7e1e22ecf87e00ec4a42a5118941f5fd4039844f6abaa0, but it hasn’t been released yet.
Never mind, misread some context.
Thanks for the report! released a fix: https://github.com/micromark/micromark-extension-mdx-expression/releases
Initial checklist
Affected packages and versions
1.2.0
Link to runnable example
No response
Steps to reproduce
A typescript project using the lib
Expected behavior
Should compile.
Actual behavior
estree-util-visit has no exported 'Node' type.
The solution is to comment the line out ?
Runtime
Node v16
Package manager
npm v7
OS
macOS
Build and bundle tools
Webpack