Closed scharf closed 8 years ago
What problems do you have specifically? I have bunch of tests and they run ok.
It's not a question of what exactly fails today.
The problem is the package (as it is configured today) introduces unpredictable behavior, since it depends on the latest nightly build, which might change or break at any time.
How about making "typescript" into a peer dependency, so that this decision can be made by the app developer instead?
Thx -- we switched to a setup where we transpile the typescript outside the meteor build process -- this gives us control over the version we are using.
When using meteor-typesctipt in a production environment it is dangerous to use "typescript": "next" which is the nightly build version of typescript.
I got version
1.9.0-dev.20160412
of typescript which causes all kinds of problems.Is there a way to install a stable version of typescript with npm that meteor-typescript then uses?