-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Consider making @types/*
dev dependencies
#1326
Comments
This cannot work today because Inquirer code accesses the node types. So it cannot ship without the I'm open to review this or change the code somewhat to get to a better result. But I'll need documentation and reference from you supporting how this is possible. We can work together on that if you're willing to. |
it looks like you only ship javascript in your package. so the types package is not directly needed. i would advise using this as a |
That is not the case, the types are shipped. See https://www.npmjs.com/package/@inquirer/core?activeTab=code under |
then a peerDependency i think might be more appropriate, with the minimum supported version of node |
This also add quite a lot of size to install the package.
|
Done in @inquirer/prompts@7.0.0 and peer releases for individual prompts. #1569 is the PR with the change. I reimplemented only the types (made them sub-types) required by Inquirer to be able to remove the direct dependency. |
It would be great if the
@types/*
were not direct dependencies but dev dependencies as to avoid the pit fall of having the types for node 20, but running under node 18.The text was updated successfully, but these errors were encountered: