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.

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

Docs: Importing Your Favorite JavaScript / TypeScript Package #560

Open
peterpme opened this issue May 4, 2020 · 1 comment
Open

Docs: Importing Your Favorite JavaScript / TypeScript Package #560

peterpme opened this issue May 4, 2020 · 1 comment
Labels
docs issues that are about providing better documentation help wanted

Comments

@peterpme
Copy link
Collaborator

peterpme commented May 4, 2020

This is a common topic among beginners: how do I do this?

We can go over:

  • using community versions of popular packages (bs-*)
  • writing your own bindings for easy packages

I think it's worth pointing out that unlike DefinitlyTyped and the TypeScript ecosystem requiring everything up front, we can say, "hey, if you only need to type x, y, z, its super easy, you don't need to install the whole thing"

@peterpme peterpme added help wanted docs issues that are about providing better documentation labels May 4, 2020
@heygema
Copy link

heygema commented May 18, 2020

so as opposed to DefinitelyTyped folks, we apparently have many separate(possibly similar) bs-* bindings in the wild. imo to improve ReasonML engagement in the community, what about shipping Reason bindings in each of those pop packages/make a repo for DefinitelyBinded (I guess, redex already sort of solved this part) haha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs issues that are about providing better documentation help wanted
Projects
None yet
Development

No branches or pull requests

2 participants