0d03fafbfe
Refactors handlers.rs The idea is that all Deno "ops" (aka bindings) should map onto a Rust Future. By setting the "sync" flag in the Base message users can determine if the future is executed immediately or put on the event loop. In the case of async futures, a promise is automatically created. Errors are automatically forwarded and raised. TODO: - The file system ops in src/handler.rs are not using the thread pool yet. This will be done in the future using tokio_threadpool::blocking. That is, if you try to call them asynchronously, you will get a promise and it will act asynchronous, but currently it will be blocking. - Handlers in src/handler.rs returned boxed futures. This was to make it easy while developing. We should try to remove this allocation. |
||
---|---|---|
.github | ||
build_extra | ||
js | ||
libdeno | ||
src | ||
tests | ||
third_party@ff175a4d08 | ||
tools | ||
.appveyor.yml | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.gn | ||
.prettierignore | ||
.travis.yml | ||
build | ||
BUILD.gn | ||
build_overrides | ||
buildtools | ||
Cargo.toml | ||
gclient_config.py | ||
LICENSE | ||
node_modules | ||
package.json | ||
README.md | ||
Roadmap.md | ||
rollup.config.js | ||
testing | ||
tsconfig.json | ||
tslint.json |
deno
Linux & Mac | Windows |
---|---|
A secure TypeScript runtime built on V8
-
Supports TypeScript 3.0.1 out of the box. Uses V8 6.9.297. That is, it's very modern JavaScript.
-
No
package.json
. No npm. Not explicitly compatible with Node. -
Imports reference source code URLs only.
import { test } from "https://unpkg.com/deno_testing@0.0.5/testing.ts" import { log } from "./util.ts"
Remote code is fetched and cached on first execution, and never updated until the code is run with the
--reload
flag. (So, this will still work on an airplane. See~/.deno/src
for details on the cache.) -
File system and network access can be controlled in order to run sandboxed code. Defaults to read-only file system access and no network access. Access between V8 (unprivileged) and Rust (privileged) is only done via serialized messages defined in this flatbuffer. This makes it easy to audit. To enable write access explicitly use
--allow-write
and--allow-net
for network access. -
Single executable:
> ls -lh out/release/deno -rwxr-xr-x 1 rld staff 48M Aug 2 13:24 out/release/deno > otool -L out/release/deno out/release/deno: /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4) /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 58286.51.6) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.0) >
-
Always dies on uncaught errors.
-
Supports top-level
await
. -
Aims to be browser compatible.
Install
curl -sSf https://raw.githubusercontent.com/denoland/deno_install/master/install.py | python
Status
Under development.
We make binary releases here.
Progress towards future releases is tracked here.
Roadmap is here. Also see this presentation.
Build instructions
To ensure reproducible builds, Deno has most of its dependencies in a git submodule. However, you need to install separately:
To build:
# Fetch deps.
git clone --recurse-submodules https://github.com/denoland/deno.git
cd deno
./tools/setup.py
# Build.
./tools/build.py
# Run.
./out/debug/deno tests/002_hello.ts
# Test.
./tools/test.py
# Format code.
./tools/format.py
Other useful commands:
# Call ninja manually.
./third_party/depot_tools/ninja -C out/debug
# Build a release binary.
DENO_BUILD_MODE=release ./tools/build.py :deno
# List executable targets.
./third_party/depot_tools/gn ls out/debug //:* --as=output --type=executable
# List build configuation.
./third_party/depot_tools/gn args out/debug/ --list
# Edit build configuration.
./third_party/depot_tools/gn args out/debug/
# Describe a target.
./third_party/depot_tools/gn desc out/debug/ :deno
./third_party/depot_tools/gn help
Env vars: DENO_BUILD_MODE
, DENO_BUILD_PATH
, DENO_BUILD_ARGS
.
Contributing
- Fork this repository and create your branch from
master
. - Make your change.
- Ensure
./tools/test.py
passes. - Format your code with
./tools/format.py
. - Make sure
./tools/lint.py
passes. - Send a pull request.
- Sign the CLA, if you haven't already.