Deno
A secure runtime for JavaScript and TypeScript.
Deno aims to provide a productive and secure scripting environment for the modern programmer. It is built on top of V8, Rust, and TypeScript.
Please read the introduction for more specifics.
A secure JavaScript and TypeScript runtime
deno A JavaScript runtime using V8 6.8 and Go. Supports TypeScript 2.8 out of the box. No package.json, no npm. Not backwards compatible with Node. Imports reference source code URLs only. import { test }
Information
| Category: JavaScript / Miscellaneous |
| Watchers: 1.6k |
| Star: 78.4k |
| Fork: 4.2k |
| Last update: Oct 21, 2021 |
Popular
717 Open
More issues
Closed
求不要更新了，老子学不动了
opened May 31, 2018 by fujiazhang 513
Closed
I was wondering if there's any plan to support compiling deno scripts into a single executable?
I saw "Single executable" as a feature, but the code that follows seems to suggest it's deno as the single executable, not the programs executed with it.
It'd be awesome to support something like go build main.go or something like zeit/pkg.
feat cli
opened Oct 13, 2018 by matthewmueller 111
Closed
Import from url is very hard to use. I think is not a good idea. If so,
- We must manage more js files not our own development.
- Heavily dependent on the network, because the third package also can import another packages.
Like C#\Java, the nuget and maven is good for use. Maybe use that mode can help us manage the packages.
opened May 31, 2018 by hstarorg 94
Closed
Update April 15, 2020: Still go for May 13.
Update March 6, 2020: There's a difficult balance to be had between trying to get it right and shipping a usable product. The repository continues to see rapid development and we have yet to make substantial progress on the major missing feature: dev tool support. Therefore we are bumping the release date yet again. However instead of blindly estimating several weeks out, we've discussed it at length and decided 2 months would be enough time. This coincidentally is around the 2 year anniversary since the first commit. Therefore we are setting the date of May 13, 2020 as the 1.0 release date. Contributors are encouraged to get any major API changes in before April 20 - after that date we will be polishing and bug fixing. Of course the API will continue to evolve and improve after 1.0, but we will be making explicit stability guarantees for some interfaces.
Update Jan 27, 2020: Massive progress is being made, but we still have not yet accomplished the major feature blocker: devtool support. I hate to keep kicking the release date, but we're still looking at some weeks of development. We hope to ship a 1.0 build with stability promises towards end of February.
Update Dec 23, 2019: There is one major feature we lack that needs to be in 1.0 - that's a way to hook Deno up to Chrome DevTools. Implementing it has induced a rewrite of the bindings to V8 - that work is ongoing https://github.com/denoland/rusty_v8. We want to fork lift Deno onto that system before 1.0 happens. Current estimate for 1.0 is end of January.
-
[x] replace libdeno with rusty_v8 https://github.com/denoland/deno/issues/3530
-
[x] "deno --debug" https://github.com/denoland/deno/issues/1120 We need to be able to debug using Chrome Devtools. As the deno userland code base grows, it becomes in increasingly painful to work without a debugger. The way this will work is with a websocket server in Rust (port 9229) which forwards messages to V8 (using V8InspectorClient). https://github.com/denoland/deno/pull/4484
-
[x] Loading and execution of modules (either JS or TS) needs to be correct. This is the main thing we deliver actually, but there are still many bugs:
source maps are sometimes incorrect https://github.com/denoland/deno/issues/2390,double downloads happen https://github.com/denoland/deno/issues/2442, the cache needs to be refactored https://github.com/denoland/deno/issues/2057. -
[X] Import maps. It's a very reasonable standard and we can provide support via a command line flag. This allows bare imports. The feature will land very soon https://github.com/denoland/deno/pull/2360.
-
[x] Dynamic import. 50% complete at the time of writing. https://github.com/denoland/deno/issues/1789
-
[x] "deno test" test runner https://github.com/denoland/deno_std/issues/193
-
[x] "deno fmt" is slow on the first run. It download a couple of large prettier bundles. https://github.com/denoland/deno/issues/2490
-
[x] We need to support d.ts files https://github.com/denoland/deno/issues/1432
-
[X] "deno bundle" outputs a single AMD bundle of your program. This is useful to share code with websites. Early work has started: https://github.com/denoland/deno/pull/2467
-
[ ]
"deno compile" is a very interesting feature to output an executable. It would be nice to have, but I would let this slip past 1.0. https://github.com/denoland/deno/issues/986Not for 1.0 -
[x] "deno install" is a program that creates little shell script aliases to deno programs in your $PATH. This let's people distribute their code easily. https://github.com/denoland/deno_std/issues/471
-
[x] dlopen / plugins / extension modules. We need some way of calling into Rust land. The way Parcel does it is pretty awesome https://parceljs.org/rust.html - but we need low-level primitives to build that on, as we need to carefully funnel everything through the Op abstraction. @afinch7 has a working patch for loading ops in DLLs https://github.com/denoland/deno/pull/2385, we are still iterating on the exact API. I would allow a true FFI module to slip past 1.0 - we'll get there - but it needs to be built on ops. https://github.com/denoland/deno/pull/3372
-
[x] Support TLS https://github.com/denoland/deno/issues/3009
-
[ ] The web-server should be faster.
-
[X] When you visit a deno.land script url (example https://deno.land/std/http/server.ts) in a web browser, it should do better than redirect. It should look at the Accept header and serve pretty HTML. Solved in https://github.com/denoland/registry/commit/b78e6ae331004859aad7b01ed452f6b00265b035
-
[X]
If you use "docs.deno.land" you will get auto-generated docs. https://github.com/denoland/deno/issues/3094https://github.com/denoland/deno_website2/pull/49 -
[x] typescript dependencies are not loaded in parallel
#2626https://github.com/denoland/deno/issues/2994 -
[x] signal handlers https://github.com/denoland/deno/issues/2339 #3757
-
[X] fs events https://github.com/denoland/deno/issues/1826 #3452
-
[ ] TS and source maps are correctly recompiled https://github.com/denoland/deno/issues/2945
-
[x] Remove tokio_util::block_on https://github.com/denoland/deno/issues/2960
-
[x] "deno test" is slow (when running on std) https://github.com/denoland/deno/issues/2789
-
[x] deno lock file https://github.com/denoland/deno/issues/200
Do any major API renames.
- [X] https://github.com/denoland/deno/issues/2384
- [X] https://github.com/denoland/deno/issues/2474
- [X] https://github.com/denoland/deno/issues/2635 clean up ErrorKinds
- [x] https://github.com/denoland/deno/issues/2767 use web standard Permission API
- [x] https://github.com/denoland/deno/issues/2730 register_op
- [x] https://github.com/denoland/deno_std/issues/562 test(name, fn)
- [x] https://github.com/denoland/deno/issues/2123 Deno.args
- [x] https://github.com/denoland/deno/issues/2934 referencing d.ts files
- [x] https://github.com/denoland/deno/issues/2553
import.metadoesn't work with bundling on browsers. We need to come up with a different scheme for branching if the script is the main. - [x] https://github.com/denoland/deno/issues/3520 window.location should be cwd?
Other minor bugs that are nevertheless blockers:
- [x] async iteration on fetch bodies https://github.com/denoland/deno/issues/2520
- [x] https://github.com/denoland/deno_std/issues/442
- [x] support onload https://github.com/denoland/deno/issues/2386
- [x] support proxy for module downloads
https://github.com/denoland/deno/issues/588https://github.com/denoland/deno/issues/2873 - [x] panic on too many open files https://github.com/denoland/deno/issues/2243
- [x] we need a way to use typescript compiler from userland
https://github.com/denoland/deno_std/issues/428#2927 - [x] 'url' variable can't be used https://github.com/denoland/deno/issues/2888
- [x] https://github.com/denoland/deno/issues/3367
- [x] https://github.com/denoland/deno/issues/3852 Can't import jspm modules
- [x] #3401 Permissionless static relative imports are dangerous
opened Jun 7, 2019 by ry 79
Closed
Okay, this project looks really interesting so far. While watching the talk I just noticed one thing that might be a problem for some developers. That's just allowing imports with relative path's (besides URLs). There are a lot of questions on the internet on how one can import a file in TS/Webpack/whatever relative to the project root. With relative paths people will end up with things like import { foo } from '../../../../modules/featureA/foo.ts'. Or was it just ../../../modules/...? What if I move my files around? Yes, you have to update your imports anyway. But figuring out how many directories you have to go up is a very tedious task on its own.
In the talk, you/Ryan talked about browser compatibility. I haven't tried out ES modules in the browser just yet. But I'm pretty sure it also supports absolute paths. Absolute in that context means relative to the web root. It would be really handy if we were able to just write import { foo } from '/modules/featureA/foo.ts'.
Of course, now there's the question: What is the root directory of a deno application? The only thing that makes sense to me right now is the folder that contains the entry file ‒ basically what process.cwd() is in node. But I also think it's fine to place the entry file in the most top-level directory of the project, isn't it?
Or is there any problem about absolute paths I didn't think about so far? What do you think about that?
opened Jun 7, 2018 by alinnert 71
Closed
Would like some scripts and documentation on how to deploy to AWS Lambda, Serverless, GCloud functions, Azure Functions, etc.
stale
opened Jan 3, 2019 by ry 60
Open
merge on approval
opened Oct 21, 2021 by ry 0
Open
opened Oct 21, 2021 by lucacasonato 1
Open
This PR implements Deno.addSignalListener and Deno.removeSignalListener APIs as disucessed in #11158
The basic usage:
const listener = () => {
console.log("SIGTERM!")
};
// Starts listening to SIGTERM
Deno.addSignalListener("SIGTERM", listener);
...
// Stops listening to SIGTERM
Deno.removeSignalListener("SIGTERM", listener);
closes #11158
opened Oct 21, 2021 by kt3k 0
Open
When running e.g. deno info https://deno.land/std/http/mod.ts, I get
Download https://deno.land/std/http/mod.ts
Warning Implicitly using latest version (0.112.0) for https://deno.land/std/http/mod.ts
Download https://deno.land/[email protected]/http/mod.ts
Download https://deno.land/[email protected]/http/cookie.ts
Download https://deno.land/[email protected]/http/http_status.ts
Download https://deno.land/[email protected]/http/server.ts
Download https://deno.land/[email protected]/_util/assert.ts
Download https://deno.land/[email protected]/datetime/mod.ts
Download https://deno.land/[email protected]/async/mod.ts
Download https://deno.land/[email protected]/datetime/formatter.ts
Download https://deno.land/[email protected]/async/deadline.ts
Download https://deno.land/[email protected]/async/debounce.ts
Download https://deno.land/[email protected]/async/deferred.ts
Download https://deno.land/[email protected]/async/delay.ts
Download https://deno.land/[email protected]/async/mux_async_iterator.ts
Download https://deno.land/[email protected]/async/pool.ts
Download https://deno.land/[email protected]/async/tee.ts
Download https://deno.land/[email protected]/datetime/tokenizer.ts
error: an internal error occured
and @lucacasonato seemed to be able to reproduce it as well. The same happens for other std modules with that URL pattern. The CLI returns with a 0 exit code though.
I am on 1.15.2 but cannot say for sure if it was just introduced by that patch or not.
bug cli
opened Oct 20, 2021 by LionC 1
Open
This is a prototype implementation of the serializable part of the API in https://github.com/denoland/deno/issues/12067#issuecomment-943272506, to gather feedback.
opened Oct 20, 2021 by andreubotella 1
Open
Discussed in https://github.com/denoland/deno/discussions/12404
Originally posted by jaydenseric October 12, 2021 There is a way to declare types when importing:
// @deno-types="./coolLib.d.ts" import * as coolLib from "./coolLib.js";— https://deno.land/[email protected]/typescript/types#providing-types-when-importing
But how do you do the same when importing within a JSDoc type?
For example in x.js:
/** @param {import("foo").Foo} foo A foo. */
function x(foo) {
// …
}
In the above situation, if Foo is a type that comes from a .d.ts file and isn't actually a named export in the ESM module, trying to import the x.js module in a TypeScript module with type checking enabled will cause a TS error: TS2694 [ERROR]: Namespace '__' has no exported member 'Foo'..
opened Oct 19, 2021 by jaydenseric 0
Contents
Resource links
Share this repo
Related Repos
💛 You can help the author become a full-time open-source maintainer by sponsoring him on GitHub. bget Download and install binaries from GitHub Relea
Ninja Keys Keyboard shortcuts interface for your website. Working with Vanilla JS, Vue, React. Demo Why? A lot of applications support that pattern, u
svelte-reactive-css-preprocess Have you ever wished you could use your svelte variables in your component's styles. Now you can! Installation npm inst
Hoon Snippets Various hoon code snippest which developers may find useful to include/use/fork for their own use cases. Hoon is Urbit's user-facing pro
Beginner-Hacktoberfest Need Your first pr for hacktoberfest 2k21 ? come on in ❓ What's Hacktoberfest 2021? Hacktoberfest is the easiest way to get int
Code Workspace: .React => .Await/ Async (consuming Api) .Css => .Media query (mobile adaptation) Application Operation Getting Started with Create Rea
arxiv-doom This is a parody of the ever-increasing amount of papers that appear on arXiv every day, it allows you to fight the one hundred most-recent
Hello, here is a repository to send you my vision of clean architecture (firstly on the front, then later on back) in different versions. For these ex
Torrent Converter (@TorrentToMagnetRobot) A Telegram bot to convert Torrent files -> magnetic link & vice versa. Works in Groups & Private. Usage git
Repetitive Typography An experimental typography animation based on a kinetic type design by Domagoj Štrok where words get duplicated several times. A
Node Dto Node Dto is a small lib, that help developer to create dto's using javascript. This package is focused only in javascript. $ npm i node-dto H
Double Pendulum Playground Interactive Double Pendulum Playground Using SVG a double pendulum is a pendulum with another pendulum attached to its end,
writable-dom Utility to stream HTML content into a live document. Installation npm install writable-dom How it works This module allows you to write m
Booth A photo booth. I made this because macOS Photo Booth wouldn't reveal external video input sources and I don't know why. ¯\_(ツ)_/¯ This works per
Building Collaborative P2P Applications with Autobase Welcome to our workshop on building collaborative, peer-to-peer applications! We're the team beh