From: Jelle Licht <jlicht@fsfe.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>,
Marius Bakke <mbakke@fastmail.com>
Cc: 34526@debbugs.gnu.org
Subject: bug#34526: Updating node.js
Date: Thu, 21 Nov 2019 14:34:55 +0100 [thread overview]
Message-ID: <87mucpic8w.fsf@jlicht.xyz> (raw)
In-Reply-To: <878soafwtt.fsf@dustycloud.org>
Christopher Lemmer Webber <cwebber@dustycloud.org> writes:
> That's fair.
>
> I have a personal project that requires that I use a newer version of
> Node (at least version 11). So if anyone has a recipe on how to get
> Node running, even the wrong way per Guix standards, maybe useful to
> post to this bug in the meanwhile? It might also still help advance
> this bug.
I tried my hand at building llhttp (again...) using our existing nodejs
+ Sucrase (an alternative TypeScript transpiler that does not have too
many dependencies), but it seems that the devs of llhttp use
semi-advanced TypeScript constructs that are at the moment not supported
by Sucrase's transformers. To be specific, I am talking about "Moving
types"[1].
Does anyone know of any other TypeScript transpilers? They do not need
to do typechecking, as long as they allow generation of (valid)
JavaScript files.
- Jelle
[1]: https://basarat.gitbooks.io/typescript/docs/types/moving-types.html
prev parent reply other threads:[~2019-11-21 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 14:36 bug#34526: Updating node.js Daniel Gerber
2019-02-18 20:50 ` Jelle Licht
2019-02-19 8:06 ` Björn Höfling
2019-02-19 16:42 ` Daniel Gerber
2019-02-19 17:00 ` Daniel Gerber
2019-02-20 13:59 ` Jelle Licht
2019-02-21 17:02 ` Daniel Gerber
2019-11-16 20:28 ` Christopher Lemmer Webber
2019-11-17 18:25 ` Marius Bakke
2019-11-20 14:26 ` Christopher Lemmer Webber
2019-11-21 13:34 ` Jelle Licht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mucpic8w.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=34526@debbugs.gnu.org \
--cc=cwebber@dustycloud.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).