-
Notifications
You must be signed in to change notification settings - Fork 44
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
Do not publish global typings to npm #20
Comments
Hi @demurgos - how do you solve this in your project? I solved it by adding the following gulp task to my project:
|
@dauledk @brianloveswords Since I switched to another lib, I did not follow this issue actively, but it seems that multiple other people upvoted this issue. I appreciate that you tried to provide type definitions, but it's been 4 months that your library is unusable with Typescript. Please consider one of the solutions I mentioned in the first post. |
We believe that this was fixed in 3.0.0. Please let us know if that is incorrect and we'll re-open the PR |
Hi,
Your package publishes global typings to npm. This causes conflicts with other (and more recent / acurate) definitions for Node. This module is simply unusable with full TS checks.
Since you use
typings
, you shouldn't even publish your typings directory but lettypings
resolve the dependencies with yourtypings.json
file.typings
is now deprecated in favor of@types
, I'd recommend to switch to@types
while fixing this issue.The text was updated successfully, but these errors were encountered: