Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Accepting TypeScript definitions #33

Closed
pspeter3 opened this issue Aug 17, 2017 · 3 comments
Closed

Accepting TypeScript definitions #33

pspeter3 opened this issue Aug 17, 2017 · 3 comments
Labels
🤷 no/invalid This cannot be acted upon

Comments

@pspeter3
Copy link

Unified seems really cool! Would you be willing to accept TypeScript definition files?
@wooorm
Copy link
Member

wooorm commented Aug 20, 2017

Thanks @pspeter3!

My view is (and solutions are) the same as Sindre om this! sindresorhus/ama#439 (comment)

👋

@wooorm wooorm closed this as completed Aug 20, 2017
@hrajchert
Copy link
Contributor

If somebody finds this issue, I'm working on some type definitions that I will eventually put on Definitely Type.

If you want to help me testing or contributing to the type definitions, all help is wanted :)

https://github.com/hrajchert/unified-typings-test

@hrajchert hrajchert mentioned this issue Nov 27, 2018
Closed
@ChristianMurphy
Copy link
Member

As of #43 TS definitions are now included with unified.

@wooorm wooorm added the 🤷 no/invalid This cannot be acted upon label Aug 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🤷 no/invalid This cannot be acted upon
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pspeter3 @wooorm @hrajchert @ChristianMurphy