nino-porcino

yup I'm looking at it, but nothing so far. Can you please confirm the correct way to build/run the project is: node server/web-server ? 2016-11-24 12:16 GMT+01:00 avi : >...

agree 100%, I am just waiting for Typescript 2.0 because [UMD Module Loaders](https://github.com/Microsoft/TypeScript/issues/2036) will make it more easy to publish a package as a module or in the global namespace...

I'm trying to make a `npm` package out of `RiotTS` right now but there are several issue because it seems that there is no easy way to publish a library...

I've migrated the whole package to npm and TypeScript 2.0, please check the documentation again as there are some small breaking changes. I did my best to make it work...

@sandrokeil what do you mean with avoiding the `any` type?

@sandrokeil that's quite correct, you are telling typescript that you don't allow implicit `any` types, so you can't write: ``` ts constructor(opts) { } ``` you have to make it...

btw, forgot to tell I've updated also the [helloworld examples](https://github.com/nippur72/RiotTS-helloworld), you might want to check `example-global` and `example-module`.

update: I've fixed some `any` signatures, so please use the latest `1.0.10`

I guess porting it to pure ES6 should be straightforward. Perhaps it could be enough to compile it for ES6 target to have type removed and make it es6 compatible....

I just did a small experiment: - compiled with TypeScript `riot.ts` into `riot.es6.js` - wrote a small tag in es6 syntax - compiled the two with babel with the following:...