unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: t@fullmeta.me
To: Remco <me@rwv.io>
Cc: help-guix@gnu.org
Subject: Re: Web development on Guix: nodejs, npm and all that
Date: Mon, 10 Jan 2022 15:16:58 +0000	[thread overview]
Message-ID: <95b291c9-b95f-488b-82b3-ebc2d3d16533@www.fastmail.com> (raw)
In-Reply-To: <877db78z9r.fsf@rwv.io>

> I haven't encountered any npm package which doesn't work when not
> installed globally yet and it seems to me that would be a bug in said
> package.

this is certainly great to hear! Thank you

I've been trying to do all setup via `guix shell --container`. Is there an easy (obvious) way to extend environment inside the container? I can --preserve etc, but doesn't look like I can easily change e.g. PATH to ensure it includes local node_modules/bin. Maybe the better way would be to have the ability to set GUIX_ENVIRONMENT to a profile that you tweak which sets env vars apprpiately. I feel like maybe I'm already asking too much of the guix shell CLI front end and maybe I'm better of reversing what relevant .scm script does setting up container's environment and just drop my modified .scm script to a project dir. I hate mucking with BASH and such - never ends well and never goes smoothly.

Anyone has suggestions? Basically at this point we are trying to go slightly above what `guix shell --container` or even `guix shell` can do. Something that I feel amounts to (in non-guix world) to running a sort of .loginrc script when you enter the environment or container.

Should I just hack some .scm at this point?


  reply	other threads:[~2022-01-10 15:19 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 [this message]
2022-01-10 23:08     ` Jelle Licht
2022-01-10 14:54 ` Dr. Arne Babenhauserheide
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=95b291c9-b95f-488b-82b3-ebc2d3d16533@www.fastmail.com \
    --to=t@fullmeta.me \
    --cc=help-guix@gnu.org \
    --cc=me@rwv.io \
    /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).