#961337 ITP: deno -- secure runtime for JavaScript and TypeScript

#961337#5
Date:
2020-05-23 12:32:48 UTC
From:
To:
Package: wnpp
Severity: wishlist

Hi,

Node.js got a redesign that is named 'deno'.

Project webpage is https://deno.land  it says

  Deno is a simple, modern and secure runtime for JavaScript and
  TypeScript that uses V8 and is built in Rust.


Nerd fun:  deno is an anagram of  node


Where it is allready possible to do

  cargo install deno


It would be cool to get  deno   with


  sudo apt install deno



Regards
Geert Stappers
DD


P.S.
IMHO means RFP   you have a uploading sponsor

#961337#12
Date:
2020-06-29 19:27:39 UTC
From:
To:
* Package name    : deno
  Version         : 1.1.2
  Upstream Author : Deno authors
* URL             : https://github.com/denoland/deno
* License         : MIT
  Programming Lang: Rust, TypeScript, JavaScript
  Description     : A secure runtime for JavaScript and TypeScript.

I intend to package Deno and maintain it. If anybody is willing to can co-maintain with me.

Thanks,
Akshat Agarwal (humancalico)

#961337#17
Date:
2020-06-29 19:40:00 UTC
From:
To:
Control: retitle 961337 ITP: deno, secure runtime for JavaScript and TypeScript
Control: owner 961337 Akshat Agarwal <humancalico@gmail.com>

Yeah, let's seen what happens.

At least is the ITP seen by the uploading sponsor.


Regards
Geert Stappers

#961337#26
Date:
2020-06-29 20:37:54 UTC
From:
To:
Il 29/06/20 21:27, Akshat Agarwal ha scritto:

Hi Akshat,

many thanks for your interest in contributing to Debian.
would you like to maintain deno within the js-team ?
We already maintain nodejs ...

Paolo

#961337#33
Date:
2021-04-10 19:38:06 UTC
From:
To:
<screenshot>
stappers@paddy:/usr/src/debian/deno
$ grep ^name Cargo.lock  | head
name = "Inflector"
name = "adler"
name = "ahash"
name = "ahash"
name = "aho-corasick"
name = "alloc-no-stdlib"
name = "alloc-stdlib"
name = "ansi_term"
name = "anyhow"
name = "anymap"
stappers@paddy:/usr/src/debian/deno
$ grep --after=1 ^Build-Depends debian/control
Build-Depends: debhelper (>= 11), rustc, cargo
Standards-Version: 4.1.3
stappers@paddy:/usr/src/debian/deno
$
</screenshot>

What cargo needs doesn't match the Build-Depends.
If uploaded, it would fail to build due missing build dependencies.


Yes, consider packaging deno for Debian (and it's derivatives)
a very interresting challenge.


Regards
Geert Stappers

#961337#38
Date:
2021-04-10 20:17:23 UTC
From:
To:
Le sam. 10 avr. 2021 à 21:42, Geert Stappers <stappers@debian.org> a écrit :

Deno is Javascript/Typescript !
Please cc and involve pkg-javascript team.

Issues are 3-fold:
- packaging cargo (rust's package manager) dependencies
- how Deno userland modules (written in typescript/javascript) are going to
be distributed
  (probably in a way comparable to how node or javascript modules are
distributed)
- https://github.com/denoland/rusty_v8
  how to make Node and Deno share the same v8. (This is where i might be
able to help).

Jérémy

#961337#43
Date:
2021-04-10 21:15:42 UTC
From:
To:
(please don't top-post)
(cc-ing to relevant bugs and teams)


Le sam. 10 avr. 2021 à 22:26, Sergey Abroskin <merdedok@gmail.com> a écrit :
https://wiki.debian.org/Teams/RustPackaging

For all that concerns userland:
https://wiki.debian.org/Javascript
In particular this is very interesting to read (because it explains what
could be bundled or not):
https://wiki.debian.org/Javascript/GroupSourcesTutorial

Debian toolchains have been upgraded (mainly by DD yadd) to cope with
bundled dependencies,
A.K.A. components. Uscan now supports this.

In my experience a huge project like Deno is going to drag sub-projects,
make them live,
and also make mistakes and depend on abandonware.
This isn't going to be a piece of cake. The more Deno and its deps are
stable, the more it's going to be easy to package.

Jérémy

#961337#52
Date:
2025-09-25 07:00:55 UTC
From:
To:
On Sat, 10 Apr 2021 23:15:42 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?=  <kapouer@melix.org> wrote:
[...]

Looks like yt-dlp is going to start requiring Deno for downloading from
Youtube:

https://github.com/yt-dlp/yt-dlp/issues/14404

#961337#57
Date:
2025-09-25 09:21:42 UTC
From:
To:
Le jeu. 25 sept. 2025 à 09:01, Andres Salomon <dilinger@queued.net> a
écrit :
https://github.com/yt-dlp/yt-dlp/issues/14404#issuecomment-3330980464).
TL,DR: yt-dlp will support using Node instead of Deno, using
--js-runtimes=nodejs flag.
I think Debian's yt-dlp will need to change its default value for that
flag, to avoid annoying issues.

#961337#62
Date:
2025-09-25 08:57:23 UTC
From:
To:
Using a shared v8 isn't going to be easy, especially with upstream
being so contradictory about it...

Do not rely on a binary libv8.a built outside of cargo.
../..
V8 is very large and takes a long time to compile. Many users will prefer to use a prebuilt version of V8. We publish static libs for every version of rusty v8 on Github.

#961337#69
Date:
2025-12-07 18:58:57 UTC
From:
To:
Just for the reference, upstream issue:
https://github.com/denoland/deno/issues/1583

Also, about the scope of related work of packaging dependencies:

*> For an idea of the scope of work here,
https://github.com/denoland/deno/blob/main/Cargo.lock
<https://github.com/denoland/deno/blob/main/Cargo.lock> *
*> has around 600 packages.*

Regards,
Shmerl.