From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id eEihL0VsJ2eUQQEAqHPOHw:P1 (envelope-from ) for ; Sun, 03 Nov 2024 12:27:49 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id eEihL0VsJ2eUQQEAqHPOHw (envelope-from ) for ; Sun, 03 Nov 2024 13:27:49 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=fsfe.org header.s=2021081301 header.b=iV4fdUtH; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=fsfe.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1730636869; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=IylCkhKHPmQY4S8SSGZehvXJ2z/bMm/8N8kqcCn9u7I=; b=bquXgQOOL8ye4HCcVvoV2iaO/VSDu09JEz/7v3u++f0p3FBY6KWssyDsMryFnH060q6CUk 3JxKK7TPTpYDVRuIt5DWpN8Xmbtew1FCpwhAsO4/sdXlY/RwGG8hBTVEEUN+MHtVaruNyo mnTf0NmjyLLxIAsYFYSHk9lahyw6ORrrLLticZzLjgF6XriLzVmB+D2KLyhheroBqQyLUe EJncGqPf80xBiBDsAICbRFwqQ6yuO60KET1TDju/3uNcL3NwnE3DH9Kbw+5FvZQbMnlaNX 7m9en/SIdfGfNzyl7c3H26tJCt8gPue8HUr4Spe3YKuiabBx8vn3vfe7an3usA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=fsfe.org header.s=2021081301 header.b=iV4fdUtH; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=fsfe.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1730636869; a=rsa-sha256; cv=none; b=jynaz6PdKbduzve59PIUN3V/TEeaTdL8dRmBC4ehu0FNMvS2DSRqTl5SKfGLO6zwXndPeS Dx622oHfx9yKcBRjoyZUl8u2EdLndy7F/EbVkrSHIb2UXZlxVHeim89u4gFvcUm4H9E+vf 8Adkm7dWfXyegiQbH0+4GMXdHhGpMKlkcGqRn7fj9wc6UTSv73ZOaxp3okcZLCmyW+5/SU O/ZD08hbeI0s4mGSWGV4QLODo0JLI2GuG5VGT2Op1PWhJaSGAaPFdHfOHz9dH5EKTa5MbV 4HTEILfkrNhPtBCB2hdM3ErxpCoFZWemuUY9P1BfftXkQD6zYns5fE8L0uM+Jg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7DFA985AB4 for ; Sun, 03 Nov 2024 13:27:49 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t7ZhP-0002eE-It; Sun, 03 Nov 2024 07:27:19 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t7ZhO-0002dk-DQ for guix-devel@gnu.org; Sun, 03 Nov 2024 07:27:18 -0500 Received: from mail2.fsfe.org ([213.95.165.55]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t7ZhM-0007XX-3s for guix-devel@gnu.org; Sun, 03 Nov 2024 07:27:18 -0500 From: Jelle Licht DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fsfe.org; s=2021081301; t=1730636833; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=IylCkhKHPmQY4S8SSGZehvXJ2z/bMm/8N8kqcCn9u7I=; b=iV4fdUtHGoouGCEWMmPd206ZfRBmV3S5W4vRXjI74z2gpAISHE8ztGfaCKg16d6WELbWIb YIZHR+YxiAZ7Xd9ju2qoUEWxu+UEk/Rr70DVoKlFr0YWipvLDEI/44NOYfo+qZCzkIciq0 4jIdIp8fdGygg1KX/OOKDxxhwdmzD/I= To: Ashvith Shetty , guix-devel@gnu.org Subject: Re: State of JS runtime environment in Guix In-Reply-To: <9NADMS.TKTW30GMLFXA2@gmail.com> References: <9NADMS.TKTW30GMLFXA2@gmail.com> Date: Sun, 03 Nov 2024 13:27:48 +0100 Message-ID: <875xp47b97.fsf@fsfe.org> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=213.95.165.55; envelope-from=jlicht@fsfe.org; helo=mail2.fsfe.org X-Spam_score_int: -70 X-Spam_score: -7.1 X-Spam_bar: ------- X-Spam_report: (-7.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx11.migadu.com X-Migadu-Spam-Score: -1.72 X-Spam-Score: -1.72 X-Migadu-Queue-Id: 7DFA985AB4 X-TUID: hTqlXgXKXArB Hi Ashvith, Ashvith Shetty writes: > Hello, > I've not come across any new issues in a long time with regards to the > state of JS runtime environment in Guix, hence this mail. > > From my observation: > > - NodeJS is severely lagging behind at 18.9.0. The current version is > 23.1.0, I've tried bumpin to 22.0.0, incrementing per patch version, > but I had to give up, because of the failing test cases which continued > even after disabling several test cases. I've just sent a patch series (https://issues.guix.gnu.org/74187) bumping our node-lts package to 20.18.0. This would be a first step to bumping it to 22.X.Y, after which I think it should be fairly easy to create and maintain an up-to-date node-current package. > - NodeJS-bootstrap is also severely lagging behind at 10.24.1. It > should be bumped to somewhere in between 14.21.3 or 16.20.2 - I don't > know much about bootstraping, but my recent attempt to bump failed > again, because of the test cases - in this case, failures from > sequential tests. AFAICT node@10 is the last version that can still be used to properly bootstrap the llhttp packages without itself depending on llhttp; We use esbuild to compile all the TypeScript to JS, and subsequently use node@10 to run this JS which in turn generates the C code that is used to build llhttp (and subsequently, Node versions after 10). If this all sounds like an example of the XY problem, that's because it is :). What we really need is _some_ way to (re)generate the C code that is a part of llhttp. If there is some other (minimalist) JS runtime that could do this, that would be a major improvement over what we currently do. > > - Some of the related packages (llhttp-bootstrap, llhttp) seem to be > contaminated WDYM exactly? > > - Internal source dependencies (that is, stuff inside `deps/` folder, > as opposed to the inputs themselves) are painful to deal with, because > they re-build every time on test-failure and take a lot of resource - > some of them can be replaced with inputs, thankfully, but some of these > dependencies (v8, simdutf, simdjson, uvwasi, etc) can contribute to > increased build time when testing locally. Now, I was able to build > some of them as a separate package variable, but the main culprit here > (v8) still isn't a external source dependency - for this, I've also > opened a issue at GitHub: Are there any things you've already started working on? I'd love to see what we can do to make this happen. > - Deno's patch needs to be bumped, but the work is still pending, and I > don't really know much about Rust or Cargo > > - I've tried adding Bun, but gave up later because of build failures. > Nixpkgs simply ELF-patches the binaries, which is probably unacceptable > in Guix? > > - Yarn, PNPM and Lerna are still not available for NodeJS I don't use any of the non-npm options, but could you check if they can be installed using (e.g.) `npm install -g --prefix="$HOME/.local` after applying the patch series that bumps node to v20? Not really relevant for guix proper, but earlier this year I pushed the npm-binary importer that could perhaps be used to package some of {yarn,pnpm,lerna} in a channel or local guix.scm. > > - There is a lack of JavaScript or NodeJS-specific maintainer team > > Given how the JS development tool is to be in a poor state, I wanted to > have a discussion about the actions that can be taken to improve this > situation. Agreed. I think the first order of business should be getting up-to-date package(s) for Node.js. >From there, we could branch out to several distinct topics, such as: - Simplifying the bootstrap story of llhttp - Unbundling more dependencies in the Node.js package - Keeping a secure LTS version of Node.js in the package repo. - Keeping a secure and recent version of Node.js in the package repo. Thanks for starting this discussion - Jelle