You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently working on building up a suite of gulp tasks and a gulpfile that are all implemented using typescript. For this, I use the compiler option "noImplicitAny": true.
Using that options will cause typescript to fail to compile my existing tasks that use remap-istanbul, as there is no type information for remap-istanbul available.
While I could define such typings myself, I'd rather would like these to be included directly into the package, so that I can reuse these typings from where ever I like. And others might also want this.
While one could publish the typings over at definitely typed, this would require a second party to maintain these typings, which is kind of counter productive.
What do you think?
The text was updated successfully, but these errors were encountered:
Thanks for working on this, it's a good thing.
Since you're writing definitions for the package, it's good that you use external module definitions but you should leave out the Node reference. Add @types/node as a devDependency because it's an environment package.
I am currently working on building up a suite of gulp tasks and a gulpfile that are all implemented using typescript. For this, I use the compiler option
"noImplicitAny": true
.Using that options will cause typescript to fail to compile my existing tasks that use remap-istanbul, as there is no type information for remap-istanbul available.
While I could define such typings myself, I'd rather would like these to be included directly into the package, so that I can reuse these typings from where ever I like. And others might also want this.
While one could publish the typings over at definitely typed, this would require a second party to maintain these typings, which is kind of counter productive.
What do you think?
The text was updated successfully, but these errors were encountered: