unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: t@fullmeta.me
Cc: help-guix@gnu.org
Subject: Re: Web development on Guix: nodejs, npm and all that
Date: Mon, 10 Jan 2022 15:54:28 +0100	[thread overview]
Message-ID: <87h7abpqkn.fsf@web.de> (raw)
In-Reply-To: <87y23niukg.fsf@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Hi t,

t@fullmeta.me writes:
> Do people do web-dev on Guix System? I need to dive back into the
> whole Node.js NPM ecosystem - something I've not touched for some 
> years and I'm wondering how people go about e.g. installing NPM
> packages on Guix.

> So, how do people program for the Web, Node on Guix. Does =npm
> install= which defaults to local installation work well enough for 
> most packages? An outline of what to expect and known problems and
> workarounds would be very useful.

I do webdev on Guix, but I work in a team where I’m currently the only
Guix user, so my usage must work with changes we do.

I used to have a setup that used the local guix-installed npm (
https://www.draketo.de/software/guix-work#npm ), but that often broke,
so I switched to copying the

node_modules/npm/bin/npm-cli.js

script from our build environment to

~/.local/bin/npm

(which I have on my path)
with #!/usr/bin/env node as hashbang.

That now actually works pretty well, and it uses the node from Guix.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  parent reply	other threads:[~2022-01-10 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 13:17 Web development on Guix: nodejs, npm and all that t
2022-01-10 14:02 ` Remco
2022-01-10 15:16   ` t
2022-01-10 23:08     ` Jelle Licht
2022-01-10 14:54 ` Dr. Arne Babenhauserheide [this message]
2022-01-10 18:15   ` Chris Marusich
2022-01-10 22:24     ` Dr. Arne Babenhauserheide

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=87h7abpqkn.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=help-guix@gnu.org \
    --cc=t@fullmeta.me \
    /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).