Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-10-04 | Merge deno_cli_snapshots into deno_cli (#3064) | Ryan Dahl | |
2019-04-21 | Fix eslint warnings (#2151) | Ryan Dahl | |
Co-authored-by: Bartek IwaĆczuk <biwanczuk@gmail.com> Co-authored-by: LE GOFF Vincent <g_n_s@hotmail.fr> | |||
2019-03-06 | Upgrade deno_std (#1892) | Ryan Dahl | |
A major API change was that asserts are imported from testing/asserts.ts now rather than testing/mod.ts and assertEqual as renamed to assertEquals to conform to what is most common in JavaScript. | |||
2019-03-06 | Reorganize version and platform into Deno.build and Deno.version (#1879) | Kevin (Kun) "Kassimo" Qian | |
2019-02-12 | Add Deno global namespace (#1748) | Kitson Kelly | |
Resolves #1705 This PR adds the Deno APIs as a global namespace named `Deno`. For backwards compatibility, the ability to `import * from "deno"` is preserved. I have tried to convert every test and internal code the references the module to use the namespace instead, but because I didn't break compatibility I am not sure. On the REPL, `deno` no longer exists, replaced only with `Deno` to align with the regular runtime. The runtime type library includes both the namespace and module. This means it duplicates the whole type information. When we remove the functionality from the runtime, it will be a one line change to the library generator to remove the module definition from the type library. I marked a `TODO` in a couple places where to remove the `"deno"` module, but there are additional places I know I didn't mark. | |||
2019-02-08 | Add --allow-read (#1689) | Dmitry Sharshakov | |
Co-authored-by: Greg Altman <g.s.altman@gmail.com> | |||
2019-02-02 | Clarify writeFile options and avoid unexpected perm modification (#1643) | Kevin (Kun) "Kassimo" Qian | |
2019-01-21 | chore: update license lines (#1557) | Yoshiya Hinosawa | |
2018-09-11 | Move writeFileSync to write_file.ts, add writeFile and tests (#728) | Kevin (Kun) "Kassimo" Qian | |