chore: Convert to Deno

[ebebbington]

Many changes:

• Removes eslint, and uses deno lint instead
• Option to use deno fmt is available
• Removed all npm dependencies, and replaces scripts with scripts for deno
• Creates a new compile.ts file, in place of tsc, which uses 2 unstable api's
• Adds .ts extensions to imports for src instead of .js (to pass emit checks)
• Remove tsconfig.json and package-lock.json as they are no longer needed
• A new examples_mod.ts inside src so we can properly emit the examples. Reason for this is, they aren't part of the dependency free for mod.ts so aren't included in the emit result. Due to this, we compile examples_mod.ts too. Not worth compiling each individual file instead because that takes a long time. As it stands, running compile.ts is faster than tsc/webpack

Of course it's completely down to you @0kku, as to whether you want to request changes, let along approve this PR, it's all welcomed and i completely understand

So how do you, Okku, and an end user use destiny now?

Good question edward

As the maintainer of Destiny, you would:

• Setup a webhook to deno.land, now anyone using Deno can import the src/*.ts files fine
• npm run compile and deploy as you usually would this generates maps, declaration files and js files, so you can import it in the browser for js files

As a user of Destiny:

• Import destiny from deno.land
• or import destiny from the destiny cdn

TODO

• Discuss examples directory: do we keep it as a test tool for @0kku? Do we migrate it into docs? (associated thread: https://github.com/0kku/destiny/pull/17#discussion_r662341221)

[0kku]

Love the latest commit message lol.

[ebebbington]

as of now, using canary (> 1.11.5) the infinite loop has gone, but revealed some more issues:

https://github.com/denoland/deno/issues/11286 https://github.com/denoland/deno/issues/11287

[ebebbington]

https://github.com/0kku/destiny/pull/17/commits/3647b7fcaf10dd06f991a3e774aba3e7e08cd500 does address both issues mentioned above, though of course it is a tiny workaround

[0kku]

3647b7f does address both issues mentioned above, though of course it is a tiny workaround

Could've just moved the cleanup method outside the class, since it's doing nothing with the instance anyway.

[ebebbington]

3647b7f does address both issues mentioned above, though of course it is a tiny workaround

Could've just moved the cleanup method outside the class, since it's doing nothing with the instance anyway.

Guess that's your preferred way then :P Is this approach something you're ok with?