-
Notifications
You must be signed in to change notification settings - Fork 563
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
Bundle TypeScript definitions #102
Comments
@bradleyayers I'm not opposed to the idea, its just a matter of the slippery slope. |
I went the DefinitelyTyped route initially, but hit a blocker because my project has two transitive dependencies on I don't know of another solution here other than bundling the declaration files in the npm package. |
@bradleyayers how will this solve that unless everyone uses this packages type definitions? |
I'm not sure I understand the question, but… TypeScript automatically uses type definitions that are bundled in NPM packages, but someone could still use @types/classnames if they want (but they probably wouldn't want to, since it's more overhead). The key difference with packaged definitions is that they don't need to introduce definitions globally. This means that multiple instances of a package can be used at the same, each providing their own definitions. |
Closing in favour of #103 |
Would you be open to bundling a .d.ts TypeScript definition for this package, so that it can seamlessly be used from TypeScript?
There are existing definitions https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/classnames that could be copied over, so it should be fairly trivial.
The text was updated successfully, but these errors were encountered: