Closed TenviLi closed 2 years ago
Feel free to fix types
I'm facing the same issue. any progress on this issue? If you don't mind, I would like to pick this issue.
I'm wondering whether hooks.[hookname].taps
property should be public.
hooks.[hookname].taps
seems to be private value used only in tapable’s inner process. (refering to hooks.[hookname].taps
does not exist in also tapable's README, not only in type definitions)
In code in screenshots, hooks.[hookname].taps
is accessed in order to copy A Hook’s taps into B Hook. in my opinion, it is better that tapable provide method to fullfill such a requisition
How do you think about this?
When I use this property
.taps
with typescript, It will prompt you that the property does not existIn fact, i found this usage in the webpack source code
tapable.d.ts
: