-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Type errors on new major version → 11.0.2 #228
Comments
Duplicate of #227 |
This comment has been minimized.
This comment has been minimized.
Hi! Thanks for taking the time to contribute! Because we treat issues as our backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn’t an exact duplicate but is closely related. Thanks, |
The ecosystem is in the process of being updated. |
Awesome - thanks guys. I'll sit tight! |
Initial checklist
Affected packages and versions
unified@11.0.2, remark-parse@10.0.2
Link to runnable example
https://github.com/philcockfield/unified-type-error
Steps to reproduce
The sample repo above is a vanilla typescript setup with
unified@11.0.2
andremark-parse
added to show typescript type error.The first 2 lines of the "getting started" sample on the Unified README are used to demonstrate the type error below, although other plugins that were successfully being used with the prior major version of unified@10.1.2 also produce similar type errors:
producing type error:
Expected behavior
Strongly typed as prior version (?? → I could not find any updated mentions in the unified README to setup types specially)
Actual behavior
The type error occurs at initial configuration of the pipeline:
Affected runtime and version
node@19
Affected package manager and version
npm@9.6.3
Affected OS and version
MacOS 13.4.1
Build and bundle tools
Vite
The text was updated successfully, but these errors were encountered: