From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Begin a dev-libs/nodejs category?
Date: Tue, 20 Mar 2018 16:44:19 -0400 [thread overview]
Message-ID: <de82a9ba-537a-a7a9-53bc-a134538536ae@gentoo.org> (raw)
In-Reply-To: <BLUPR17MB02737BD97DF18E8F5C8F6801D9AB0@BLUPR17MB0273.namprd17.prod.outlook.com>
On 03/20/2018 04:14 PM, Herb Miller Jr. wrote:
> That is scary. I hadn't noticed there are node_modules directories under
> many node modules and that npm list outputs different versions of the
> same dependency. To help me better understand the situation, when you
> see this happen does "bar-1.0" normally depend on "baz-1.0" because...
>
> A) There is some huge technical hurdle in upgrading to "baz-2.0"?
> B) I was too lazy or didn't care to upgrade to "baz-2.0"?
> C) My package.json is outdated?
>
> If A, can you point me to a good example I can take a look at?
It's usually B or C, but I hit several cases where there was a real
incompatibility. When I opened Github issues, I got a lot of WONTFIX
responses telling me that I have to use npm.
No particular examples come to mind, though -- this was about 2.5 years ago.
next prev parent reply other threads:[~2018-03-20 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:50 [gentoo-dev] [RFC] Begin a dev-libs/nodejs category? Herb Miller Jr.
2018-03-20 18:34 ` Michał Górny
2018-03-20 19:43 ` Herb Miller Jr.
2018-03-20 18:48 ` Michael Orlitzky
2018-03-20 20:14 ` Herb Miller Jr.
2018-03-20 20:44 ` Michael Orlitzky [this message]
2018-03-21 1:27 ` Kent Fredric
2018-03-21 1:36 ` M. J. Everitt
2018-03-20 23:50 ` Benda Xu
2018-03-21 1:44 ` Herb Miller Jr.
2018-03-21 7:33 ` Kent Fredric
2018-03-21 12:22 ` Herb Miller Jr.
2018-03-21 10:07 ` X dej
2018-03-21 12:15 ` [gentoo-dev] Pypi generator (Was: [RFC] Begin a dev-libs/nodejs category?) Benda Xu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de82a9ba-537a-a7a9-53bc-a134538536ae@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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