Home / JavaScript / Miscellaneous

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.5k
Star: 87.6k
Fork: 4.7k
Last update: Feb 1, 2023
Resource links
https://github.com/denoland/deno
Popular
1111 Open More issues
Closed

求不要更新了，老子学不动了

求不要更新了，老子学不动了

opened May 31, 2018 by fujiazhang 513
Closed

"deno compile" into executable

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

Maybe need a package management tool

Import from url is very hard to use. I think is not a good idea. If so,

  1. We must manage more js files not our own development.
  2. 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

1.0

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/986 Not 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/3094 https://github.com/denoland/deno_website2/pull/49

  • [x] typescript dependencies are not loaded in parallel #2626 https://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.meta doesn'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/588 https://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

import with absolute path?

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 72
Closed

Skip type checking by default

Discussed in https://github.com/denoland/deno/discussions/8549

Originally posted by kitsonk November 30, 2020 Instead of --no-check consider type checking TypeScript as an opt-in with a --check option.

The core team has discussed this and reviewed the feedback from the community. Based on that, we are going to move forward with the following:

  • The --check flag will be implemented for the appropriate subcommands. This will use the built-in tsc for type checking and use tsc for the emit (except for bundles where we will use swc). We may in the future use swc for the emit here as well. This is basically the current default behaviour of Deno.
  • The --no-check flag will be deprecated and issue a warning that it is deprecated. The behaviour will not change from its current for now.
  • The default behaviour of the command line will be changed so that the code is not type checked and emitted using swc (this is basically the behaviour of --no-check now).

We will raise the PRs necessary to implement this and tentatively aim to introduce this in 1.13.

Why are you doing this?

The goal of the Deno CLI is to be a fun and productive scripting language. A user should be able to hack on some code and quickly see the results of their endeavour. The more "hurdles" that are in the way, the less fun and productive the experience becomes. We ❤️ TypeScript, we want people to use TypeScript more and more, but there are two major challenges with that:

  • Type checking is relative slow and expensive. We have tried (almost) everything to speed it up (see: #5432) but a relative small program still takes a second or two to type check, while just transpiling the TypeScript with --no-check takes under 100ms.
  • Deno terminates if it encounters a type check diagnostic. That is on us. We should have maybe always treated them as warnings and still executed the output anyways, but we didn't. We could of course change that now, but the problem then is the point above. We don't feel there is a huge amount of value to users to just address this point.

While on the surface it might seem like we are "watering" down Deno, we are motivated to make it easier to use Deno. If you are just starting out, maybe not having used TypeScript in strict mode before, or are just trying to hack a few lines of TypeScript and don't have all of your type annotations right, or you have imported a 3rd party library whose globals conflict with another 3rd party library, you have to spend all your time sorting that out to just find out if your code runs. Again, that isn't fun for anyone and certainly isn't productive.

Also, we have tried to put a lot of effort into the language server, and realistically that is where most people type check their code anyways, in their editor, which means to the majority of people type checking is not the default need they have when running on the command line. It is something they need as a final check, maybe in their CI, maybe before they commit, not every time they want to see if the code runs.

So, we acknowledge that in the discussion there wasn't overwhelming broad support for this, but we think we need to do this not for those already using Deno on a daily basis, but for those experimenting with Deno and TypeScript.

feat cli maybe 2.0 
opened Jul 8, 2021 by kitsonk 61
Closed

Wanted: serverless deno configuration

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

feat(compile): Enable multiple roots for a standalone module graph

This change will enable dynamic imports and web workers to use modules not reachable from the main module, by passing a list of extra side module roots as options to deno compile.

This PR builds on top of #17657, which adds support for web workers to deno compile.

The option name --extra-side-modules is up for bikeshedding, as well as the exact way to specify such list of modules. I suspect this list could be added to deno.json.

opened Feb 5, 2023 by andreubotella 0
Open

deno-fmt Allow imports to be customized to a single line imports

Hello guys, I would like to propose a new rule or to modify the existing one for lineWidth to allow imports to be preserved to a single line.

  1. Proposal for new rule: as described in this PR from dprint
  2. Propasal for changing existing rule as per a similar rule from eslint
   "lineWidth": [
      {
        "width": 80,
        "ignorePattern": "^import"
      }
    ]

I understand no-one wants to add new rules or configs to an opinionated formatter, but this doesn't need to be a new rule necessarily.

opened Feb 5, 2023 by PodaruDragos 0
Open

chore(cli): stabilize coverage, doc, shuffle flags

This PR removes the UNSTABLE mentions from the CLI docs for deno test --coverage/doc/shuffle.

Fixes https://github.com/denoland/deno/issues/17659.

opened Feb 5, 2023 by GJZwiers 0
Open

Suggestion: stabilize remaining unstable flags of `deno test`

The CLI docs for deno test have three flags still listed as unstable: --coverage, --doc, and --shuffle. All of these have been around for quite some time and they seem to be working well, so perhaps they could be stabilized?

opened Feb 5, 2023 by GJZwiers 1
Open

Dynamic imports require net access even when they are unused 

if (false) {
	await import("https://deno.land/[email protected]/node/module.ts")
}

> % deno run foo.js
⚠️  ┌ Deno requests net access to "deno.land".
   ├ Requested by `import()` API
   ├ Run again with --allow-net to bypass this prompt.
   └ Allow? [y/n] (y = yes, allow; n = no, deny) >

I feel like it's only supposed to request access the moment the await import() is called, or am I missing something?

For the moment a workaround is to keep the import specifier in a separate variable:

if (false) {
	const str = "https://deno.land/[email protected]/node/module.ts";
	const mod = await import(str);
}

But this removes type safety and turns mod into any.

opened Feb 5, 2023 by jespertheend 1
Open

feat(compile): Add support for web workers in standalone mode

opened Feb 5, 2023 by andreubotella 0
Open

fix(deno_node/require): Fix error with require.resolve when called with paths option

When running the following code from a node module, an error occurs:

require.resolve('anything', {paths:['any path']})

Error: Empty filepath.
    at pathDirname (deno:ext/node/02_require.js:50:13)
    at new Module (deno:ext/node/02_require.js:257:17)
    at Function.Module._resolveFilename (deno:ext/node/02_require.js:566:30)
    at Function.resolve (deno:ext/node/02_require.js:824:21)

This is caused by using an empty string for the fake package's id:

https://github.com/denoland/deno/blob/a09296322e1fd4451e903515a497d9e02e14ace6/ext/node/02_require.js#L566

while at the same time enforcing package id to be non-empty:

https://github.com/denoland/deno/blob/a09296322e1fd4451e903515a497d9e02e14ace6/ext/node/02_require.js#L48-L51

Since the fake package is only used for package resolution and its id and path are not used anywhere, I just filled it with "fake-module" and the above error is gone.

Related issue: https://github.com/denoland/deno/issues/17175 https://github.com/denoland/deno/issues/17176

opened Feb 5, 2023 by b123400 1

Contents

    denoland deno — A secure JavaScript/TypeScript runtime built with V8, Rust, and Tokio
    chmike Fast, secure and efficient secure cookie encoder/decoder
    elsaland Elsa is a minimal, fast and secure runtime for Javascript and Typescript written in Go
    m0bilesecurity Runtime Mobile Security (RMS) is a powerful web interface that helps you to manipulate Android Java Classes and Methods at Runtime
    dotnet Docker images for .NET Core and the .NET Core Tools.
    tevjef Collect golang runtime metrics, pushing to InfluxDB or pulling with Telegraf
    marshyski Quickly secure UNIX/Linux systems
    dtaniwaki Upload files securely
    plasmoapp A Paper fork with secure feature seed based on Secure Seed mod by Earthcomputer
    fhinkel Collect runtime type information 😻 of your JavaScript code.
    SamuelTulach Simple EFI runtime driver that hooks GetVariable function and returns data expected by Windows to make it think that it's running with secure boot enabled (faking secure boot)
    QuarkContainer Quark Container is high performance secure container runtime
    vertexclique Proactive IO & Runtime system
    ipetkov conch-runtime - A library for evaluating/executing programs written in the shell programming language
    ownalazzam10 A Powerful TypeScript Library For Creating Beautiful UIs and Secure, Fast Web Apps
    jitsi Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
    Caligatio A JavaScript/TypeScript implementation of the complete Secure Hash Standard (SHA) family (SHA-1, SHA-224/256/384/512, SHA3-224/256/384/512, SHAKE128/256, cSHAKE128/256, and KMAC128/256) with HMAC.
    seek-oss Zero-runtime Stylesheets-in-TypeScript
    slimtoolkit DockerSlim (docker-slim): Don't change anything in your Docker container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)
    agens-no Sign, verify, encrypt and decrypt using the Secure Enclave
    JamesTheHacker PassMan is a secure, and easy to use password manager that runs on the terminal! Written in bash.
    Share this repo

    Related Repos


    Miscellaneous
    5.5k
    Apache OpenWhisk is an open source serverless cloud platform
    apache OpenWhisk OpenWhisk is a serverless functions platform for building cloud applications. OpenWhisk offers a rich programming model for creating serverl
     
    Miscellaneous
    11
    Replaces twitter NFT idiocracy
    4ndv HexaGone HexaGone allows you to revert or customize twitter's new hexagonal avatars. It's a collection of a several userscripts, with different clip m
     
    Miscellaneous
    6
    replaces the nft avatars on twitter with subway jared
    virginteen replace-nft-avatars a chrome extension that replaces the nft avatars on twitter with subway jared to install Download this repo (Code > Download ZIP).
     
    Miscellaneous
    5
    Smart Contract Viewer for VS Code
    MetaplasiaTeam Contract Viewer English | 中文 Contract Viewer 是一个 VS Code 扩展，他可以帮你从区块链浏览器下载合约代码，只需要一个合约地址即可下载。 目前仅支持以太坊使用 Solidity 的智能合约，后续会支持更多类型。 快速开始 配置一个 API 在 Erh
     
    Miscellaneous
    5
    Video calling using WebRTC
    mehditeymorian webrtc-video-call This project is a video calling application using WebRTC technology. It contains minimum requirements to provide a group video call.
     
    Miscellaneous
    3
    A multipurpose bot, a clan bot, a all in one bot. The one bot u need for ur server origina...
    Tomato6966 Multipurpose-discord-bot A multipurpose bot, a clan bot, a all in one bot. The one bot u need for ur server originally made as Milrato discord Bot and
     
    Miscellaneous
    334
    A template for site builders and low-code tools.
    vercel Platforms Starter Kit The all-in-one starter kit for building platforms on Vercel. Introduction · Guide · Demo · Contributing Deploy Your Own Read the
     
    Miscellaneous
    152
    A Raycast/Alfred/Spotlight alternative
    ospfranco sol A Raycast/Alfred/Spotlight alternative Don't bother trying to run this, it's WIP, right now only the basic UI is there, no logic, there many bugs/
     
    Miscellaneous
    73
    Self hosted media tracker for movies, tv shows, video games, books and audiobooks
    bonukai MediaTracker · Self hosted platform for tracking movies, tv shows, video games, books and audiobooks, highly inspired by flox Demo https://mediatracke
     
    Miscellaneous
    52
    Everytime I come across good Github profiles I index them here
    championswimmer awesome-devs Everytime I come across good Github profiles I index them here NOTE: If you are on the github repo currently, go to the website 👇 to see
     
    Miscellaneous
    49
    Minimalist template for foundry projects
    ZeframLou Foundry template This is a template for a Foundry project. Installation To install with DappTools: dapp install [user]/[repo] To install with Foundry
     
    Miscellaneous
    45
    Log in the node terminal from the browser
    patak-dev vite-plugin-terminal Log in the node terminal from the browser Open a playground online in StackBlitz Install npm i -D vite-plugin-terminal Add plugin
     
    Miscellaneous
    43
    A simple web3 app for minting NFTs
    fireship-io Web3 - Full Tutorial The demo contains a basic web3 app and smart contract for minting NFTs. See it in action in the Web3 NFT Tutorial on YouTube. Fol
     
    Miscellaneous
    28
    A three.js component library for Svelte.
    grischaerbe A three.js component library for svelte. Index What is threlte? Getting started Concepts Interactivity Viewport Awareness Reactivity Conventions Refer
     
    Miscellaneous
    26
    Wordle Svelte Clone
    tayfunerbilen Wordle Svelte Clone Son zamanlarda popüler olan WORDLE uygulamasını svelte ile yapmaya çalıştım. Bu tarz acaba yapsam nasıl yapardım uygulamarı bana ç