Rename docker examples to TypeScript

[glensc]

Wanted to add an interface for #337 but noticed the docker examples are .js not .ts files.

There's one ts-ignore added (process.on("unhandledRejection")), because the typing doesn't match. I preferred this rather than commenting out the block.

[glensc]

@evantahler could you enlighten why examples use relative paths in git repo?

import { Worker, Scheduler } from "../../../src";
/* In your projects:
import { Scheduler, Worker } from "node-resque";
*/

why can't this be flipped over? so that most users when they copy the files, don't have to modify them to get them to work.

for example, had to make uncommitted changes to docker examples to test that the containers work properly.

[evantahler]

I believe that it is generally poor form to 'run' typescript in production, and that the recommended approach is to compile it first and then run the generated javascript files. That's why these docker examples only attempt to run the JS code which would be pre-compiled... which comes from the node-resque NPM package. We build the javascript and that's the main export of the published package.

That said, you are totally correct and the import statements should just use node-resque normally (not relative paths). In these examples we should be using the node-resque package already published to NPM, not the local version.

References:

• Should I use it in production? TypeStrong/ts-node#104
• https://www.reddit.com/r/typescript/comments/d0zku2/using_tsnode_in_production/
• https://medium.com/javascript-in-plain-english/typescript-with-node-and-express-js-why-when-and-how-eb6bc73edd5d

[evantahler]

I'll take a pass at updating these today

[evantahler]

closing this in favor of #343