-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
outdated types in @types/yeoman-environment #273
Comments
This issue is stale because it has been open with no activity. Remove stale label or comment or this will be closed |
Commenting to remove stale label. This is still needed. |
@a-b-r-o-w-n is there something specific missing in |
It looks like |
Hi, this still hasn't been resolved. Is anyone actively working on this? |
Yes I'm running into this as well. I thought I was overlooking something. |
I'm not even sure which version it's based on, maybe v2.x.x. If I get the time, I'll try to contribute back some updated types although the docs site isn't terribly informative, especially around the |
I also ran into this and got quite frustrated. Writing Yeoman generators is already a bit difficult, but writing a custom cli Frontend for a set of generators is nearly impossible if Your Typescript compiler tells you there are issues that practically only exist in the type definition files, but not in the code of itself. Still thanks a lot for developing and maintaining Yeoman, it seems to be one of the only reasonable tools on the market (besides degit, which has a different approach). |
I finally found some time to refactor the type declarations of |
That's amazing! Thank you @manuth, I'll take a look now. |
yeoman-enviroment has built-in types now. |
The latest release of the @types/yeoman-environment package is 2.10.2
I know the major was just bumped a week ago, but any chance we can get the typings updated soon?
The text was updated successfully, but these errors were encountered: