Replace usage of yarn with ni? #127
abevoelker
started this conversation in
Ideas
Replies: 2 comments
-
Good idea, that or just replacing it with |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yeah that might be more straightforward. Presumably there’s a reason yarn
is being preferred by many Rails projects (e.g. the Turbo install task also
uses it) but I don’t know why. It’s definitely a fly in the ointment though
for those of us not using it
…On Wed, Aug 17, 2022 at 1:32 PM sandstrom ***@***.***> wrote:
Good idea, that or just replacing it with npm which is still the de-facto
standard node package manager (it has it's flaws, but it works well enough
and everybody knows how to use it).
—
Reply to this email directly, view it on GitHub
<#127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABFO46ZKV7ADPV5LGWQOBLVZUV2PANCNFSM55NKDYNQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are some past issues/discussion about replacing yarn (#68, #3, #6, maybe more) with npm or pnpm (I myself just use npm).
ni is a tool that uses whatever JavaScript runtime the user has available at the time and supports npm, yarn, pnpm and bun. I wonder if it would be a good fit for JS Bundling since then it can just punt to whatever the user is using in their Rails project. The downside is it would be an additional dependency, however JS Bundling already requires yarn for people who don't use it.
It would replace these calls like this:
to these, respectively:
Beta Was this translation helpful? Give feedback.
All reactions