Jan Küster

Slightly related: #209 because if you setup an issue template in the `.github` repository then this issue template is applies to all repositories in the org

Yes you could easily add an `index.d.ts` and I think we could even add `tsc` as dev dependency and a script to build typescript types from source. Are you experienced...

> I tried to publish a package with this yesterday and I used the same technique you mentioned in the description of this issue (adding tsc as a dev dependency...

Hm I think we should have another issue for this one :thinking:

Related: https://github.com/babel/babel/issues/14227

Thank you @balosh-daniel I will try it out.

Hey @dhowe big apologies, I somehow did not see this issue being opened. I will have to review and redo the exports since the last time I worked on this...

@polygonwood you can create a PR to link it in the README if you like.

@mikkelking would you mind to check the failing tests? The backend lint issues should be fixable using `meteor npm run lint:fix` and for the tests please make sure your changes...

we should afterwards update collection2 as it still has this package as dependency, causing some package conflicts on my local setups from time to time