Jan Küster

I think a good starting point for moving towards TS would be to add type definitions at least, so intellisense can pick it up better.

Great @rashmod !!! Please do one PR per package (Thie repo contains multiple packages). Since you are new it may be a good start by using a smaller package. Another...

I woul say use `const` and `let` and all newer Methods from `Object` / `Array` and `String` that became available since ES6 (where applicable). Also favour destructuring and named parameters...

I just checked and the main Meteor project uses the @quave/quave config (see their package.json) which is maintained by @filipenevola so I think we should also adapt to use it....

I am unfortunately only on Linux and MacOS so I cannot be of much help regarding windows setup. Have you checked the Meteor forums about these issues? IIRC there should...

You need to move into the test-app directory. It contains the package.json file. The contribution.md file covers the commands you can use there. This is to separate the test project...

Just a comment in perspective - it has been requested some times to remove jQuery. The `parseHTML` is currently a crucial part of Blaze but relies on jQuery. Nothing wrong...

@znewsham is there anything you need in order to improve on this? If you add me to your repo I can help to continue this PR

I will not remove jQuery yet but I can fix the merge conflicts and add some tests so the pr can be merged soon 🙂

Hey @znewsham I am getting back at this one, finally. What would I need to do in order to tests this one in a running app using Blaze?