Welcome to Deno Newsletter issue #32!
Every Monday we serve you with a bunch of useful information and links for every Deno enthusiast.
Don't forget to join discussion on Deno's official Gitter channel!
If you encounter anything Deno related that you want to share with community, mention us on Twitter @DenoNews, or just respond to this mail.
Development
[tweet https://twitter.com/deno_land/status/1168613331172777984]
There was no release last week, but major refactors had taken place that bring us closed to 1.0!
- Long standing problem was use of Flatbuffers for serialization of data between Rust and V8 - ie. serialization of "ops". Although Flatbuffers are fast, they're also very complicated to use and significantly increase complexity of build process. However Flatbuffers are no more! After reorganization of dispatch mechanism and porting ops code Deno now uses JSON for all serialization except super-hot "read"/"write" ops which use custom minimal binary format. Whole operation was done without significant performance impact! Read more about it in #2796, #2799 and #2801
- New snapshot infrastructure - landed just yesterday #2825 this PR resolves quite a few issues that were haunting us for some time now; removing dependency on Node in build, relying on Rollup to generate main Deno bundle, slow incremental builds. Thanks to new "deno_typescript" crate (expect this name to change) users will be able to generate custom V8 snapshots easily. All of those changes are preliminary work towards using "cargo" as main build frontend (#2608).
- New features in REPL - alike Node.js REPL, Deno REPL now stores result of last evaluation in `_` variable and last thrown error in `_error`. See #2843 and #2845 for details.
- window.queueMicrotask - push a function directly to microtask queue without need to create a Promise - #2844
- Better error stack traces for async ops #2820
- Finish whatwg spec compliant console implementation #1351
- Use `reqwest` as internal HTTP client - this change adds support for using system proxies (via `HTTP_PROXY` and `HTTPS_PROXY` env variables) for downloading modules and making requests using "fetch" interface; as well as handling of gzipped responses - for more details see #2822
Registry
[caption align=”alignnone” width=”980”]
Deno Registry now supports directory listing and breadcrumbs thanks to Jed Fox (@j-f1)
Conferences
[tweet https://twitter.com/TypeScriptConf/status/1161701101667835905] [tweet https://twitter.com/kitsonk/status/1166149336742318080]
Resources
⏳ Modern JavaScript date utility library ⌛️.
Thanks for reading and stay tuned for more news next week!
- Bartek