From: Julien Lepiller <julien@lepiller.eu>
To: divoplade <d@divoplade.fr>,help-guix@gnu.org
Subject: Re: Is there a NPM importer?
Date: Mon, 18 May 2020 17:00:06 -0400 [thread overview]
Message-ID: <D0D6CF9C-6804-4EDC-8726-1508E2E08293@lepiller.eu> (raw)
In-Reply-To: <bac43d15556704bfa071edb048a3a9ce0c4a0d66.camel@divoplade.fr>
Le 18 mai 2020 16:48:24 GMT-04:00, divoplade <d@divoplade.fr> a écrit :
>Le lundi 18 mai 2020 à 16:21 -0400, Julien Lepiller a écrit :
>> When considering build-time dependencies, there are many cycles that
>> makes an importer almost impossible to create. There is some code
>> that works (at least it used to work) when you don't need a recursive
>> import, but it would be useless because most packages require
>> thousands of packages at build time.
>I am trying to know if it would be feasible to package rdflib and
>solid-auth-client. Debian has managed to do some work about it
>https://wiki.debian.org/Javascript/Nodejs/Tasks/rdflib, I don't know
>how good it is.
>
>When I pull them, npm says it 'added 144 packages'.
>
>I am not an expert in npm, but if I install whatever is under
>node_modules, I reach a convergence at 194 packages.
>
>I am not sure how to count the build packages, but I like the idea of
>discarding tests and minifiers. Maybe that would help.
>
>So, is the framagit version the latest work?
194 is only the count for runtime packages. We might be lucky and no other package might be needed.
The framagit version is my latest work, but I think there is more recent work elsewhere. I don't remember where exactly though.
next prev parent reply other threads:[~2020-05-18 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 19:00 Is there a NPM importer? divoplade
2020-05-18 20:21 ` Julien Lepiller
2020-05-18 20:48 ` divoplade
2020-05-18 21:00 ` Julien Lepiller [this message]
2020-05-19 7:12 ` divoplade
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=D0D6CF9C-6804-4EDC-8726-1508E2E08293@lepiller.eu \
--to=julien@lepiller.eu \
--cc=d@divoplade.fr \
--cc=help-guix@gnu.org \
/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.
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).