Deno: upgrade to latest typescript

Created on 26 Jul 2018  路  4Comments  路  Source: denoland/deno

  1. edit version here: https://github.com/ry/deno/blob/6b49944da1e7b06aeba04b1c0ded8e3fdb3c436b/package.json#L21
  2. run ./tools/sync_third_party.py
  3. commit changes in third_party repo. send a pull request to https://github.com/ry/deno_third_party (only add relevant files - there may be others that were mistakenly not committed yet)
  4. fix any errors: ./tools/test.py out/debug
  5. run tools/format.py
  6. send me a PR.

This is probably harder than just upgrading. Potentially difficult but good intro to runtime.ts.

Most helpful comment

Fixed in 36fa1cea4a6c7c4ae5ac93974843fcdcd4557fef

All 4 comments

From the experience with Deno 1, there is this issue: Microsoft/TypeScript#24638 which is only resolved in TypeScript 3.0 (which is in RC at the moment and should be released any moment).

Been looking at 3.0.0-rc in advance of its initial release. There was a restructuring of the built in libs, and lib.d.ts now "drags in" scripthost, webworker and dom libs. I tried to use --noLib which might actually be better for deno longer term, but the problem with that at is runtime.ts is only using single module compiling which means additional files (like lib.esnext.d.ts) can be specified.

Updated the WIP PR. Found it was easier to introduce lib.deno.d.ts and have the language service that is created at runtime use it as the default library. Now the runtime typings should better align to what is actually available and lib.deno.d.ts becomes the place where the global runtime environment for deno is described and applied to executed code.

Fixed in 36fa1cea4a6c7c4ae5ac93974843fcdcd4557fef

Was this page helpful?
0 / 5 - 0 ratings

Related issues

CruxCv picture CruxCv  路  3Comments

sh7dm picture sh7dm  路  3Comments

zugende picture zugende  路  3Comments

metakeule picture metakeule  路  3Comments

ry picture ry  路  3Comments