A secure JavaScript and Typescript runtime built on v8
https://deno.land/
Deno comes with a linter, a code formatter, a unit test runner and language server protocol, among other features. It has a standard library with limited compatibility with Node.js.
- Devel package for openSUSE:Factory
-
3
derived packages
- Links to openSUSE:Factory / deno
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:javascript/deno && cd $_
- Create Badge
Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename | Size | Changed |
---|---|---|
_constraints | 0000000427 427 Bytes | |
_link | 0000000124 124 Bytes | |
_service | 0000001021 1021 Bytes | |
_servicedata | 0000000230 230 Bytes | |
deno-2.1.2.tar.zst | 0100002260 95.4 MB | |
deno-disable-lto.patch | 0000000550 550 Bytes | |
deno.changes | 0000281944 275 KB | |
deno.obsinfo | 0000000093 93 Bytes | |
deno.spec | 0000005305 5.18 KB | |
registry.tar.zst | 0140268290 134 MB |
Comments 27
nondeterministic build issue:
https://github.com/denoland/deno/issues/9244
(For various reasons.)
rusty_v8
is fine. A major difference is thatrusty_v8
includes debug symbols, whereas deno and jstime are being stripped. It is possible that in-determinism is coming from the stripping processSee
torque.rsp
in the github thread for another nondeterminism issue.This package is not in Factory because it requires python 2.
See: https://build.opensuse.org/request/show/869869#comment-1407241 for more info
NodeJS and its v8 is building with Python 3 for some time. Maybe this needs another look to make sure it's still valid.
Thanks for the heads up. Per the notes, the
deno
build requiring Python 2 is related to upstream Chromium problems: https://github.com/denoland/rusty_v8/#build-v8-from-sourceEDIT: deno requires python3 now
Looks like deno is on python 3 now:
https://github.com/denoland/rusty_v8/commit/9cc57eb44dde6324ec36b75727c6fee638bb07c5
SR open to Factory:
https://build.opensuse.org/request/show/984060
1.8.3
->1.9.0
x86_64 builds failing on disk space errors for a while now (since 1.9.0 -> 1.9.2 checkin):
and
Still having problems with
1.10.1
EDIT: resolved (via build service mailing list)
Happening again after 1.12 checkin
EDIT 7/26: if anyone needs the x86_64 binaries, please drop a note here and I'll follow up with the appropriate mailing list. For my own personal needs, I am just building locally for now. ARM binaries are unaffected.
EDIT 8/29: Builds fixed by increasing requested disk space for x86_64
deno 1.13.0
1.14.3 -> 1.15.3
Still this package maintained? There are few updates at original source. I'm newbie in OpenSUSE, sorry for not understand totally the package maintain subject.
I've been trying to build and getting various errors in my local build
Thanks for the info
Thanks to @Guillaume_G the builds are rolling again. Upgrading to 1.30.0 🔜
1.31.2 blocked on rust1.68 to factory. it uses the (then unstable)
pin_macro
cmake
build error (1.36.1) due tolibz-ng-sys
Skipping
1.36.3
due to reversion ofrusty_v8
.Up to next version when new
deno_core
lands:https://github.com/denoland/deno_core/pull/159
node/npm compatibility. webpack fails due to incomplete
vm
implementation:https://github.com/denoland/deno/tree/main/ext/node/polyfills#deno-nodejs-compatibility
In the middle of restoring my computer after failure due to power surge. If anyone wants to submit a request, feel free to e-mail me with any questions.
Working on rebasing the upgrade command removal patch
TODO. Based on hiding
tools::upgrade
: https://github.com/search?q=repo%3Adenoland%2Fdeno%20%2Ftools%3A%3Aupgrade%2F&type=codei will probably take a look at this tomorrow since deno 2.0 came out
thank you. the current blocker is rusty_v8 failing to build.
https://github.com/denoland/rusty_v8/issues/1587
sure. i will investigate. in the meantime, it's still a release candidate so i guess i have more time
2.0 tagged
https://github.com/denoland/deno/pull/26063
live stream in 12 hours
https://www.youtube.com/live/d35SlRgVxT8
are you member of discord server by any chance?
yes, I am there, though I only check it occasionally (once every 2-3 months)