Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 20:34
    JoshuaVSherman commented #1651
  • Jan 31 2019 20:32
    JoshuaVSherman commented #1651
  • Jan 31 2019 19:42
    bthompson90 commented #1994
  • Jan 30 2019 21:33
    anishmittal2020 commented #1994
  • Jan 29 2019 23:51
    ljharb commented #1994
  • Jan 29 2019 23:51
    anishmittal2020 commented #1994
  • Jan 29 2019 23:49
    anishmittal2020 commented #1994
  • Jan 29 2019 22:05
    Tbhesswebber closed #1997
  • Jan 29 2019 22:05
    Tbhesswebber commented #1997
  • Jan 29 2019 22:03
    ljharb commented #1997
  • Jan 29 2019 22:01
    Tbhesswebber edited #1997
  • Jan 29 2019 21:59
    Tbhesswebber opened #1997
  • Jan 29 2019 18:14
    ljharb labeled #1995
  • Jan 29 2019 18:14
    ljharb labeled #1995
  • Jan 29 2019 18:14
    ljharb labeled #1995
  • Jan 29 2019 18:14
    ljharb commented #1995
  • Jan 29 2019 12:40
    abhishek6262 edited #1996
  • Jan 29 2019 12:39
    abhishek6262 edited #1996
  • Jan 29 2019 12:39
    abhishek6262 opened #1996
  • Jan 29 2019 11:59
    promcoder commented #308
Sam Korn
@sako0938

@charginghawk I am using this currently in my dockerfile:<code> ENV NVM_DIR /root/.nvm
ENV NODE_VERSION 8

#7

RUN curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.6/install.sh | bash \
&& source $NVM_DIR/nvm.sh \
&& nvm install $NODE_VERSION \
&& nvm alias default $NODE_VERSION \
&& nvm use default \
&& npm install http-server </code>

Jordan Harband
@ljharb
@sako0938 there's no "select an architecture"; if nvm won't install on your arch, and there's no node compiler flags that can make it do so, then your arch isn't supported by node
Sam Korn
@sako0938
My architecture is supported, ended up just not using nvm and including the lts binary for my architecture within my repo. My problem is related to having a different system building the image than actually running it.
Jordan Harband
@ljharb
ah. yeah that's just always going to cause problems
your build machine should always be identical to your production machine, for tons of reasons
William Hetherington
@willwh
hi guys, I have the strangest problem, really perplexed; I'm using something like the following to attempt to check if the current node version is set to what I have in an ansible playbook.....
i.e. this should exit code 0; nvm ls | grep -e 'default -> v8.9.3'
('cause I have v8.9.3 set as the default right now) 
➜ nvm ls                           
         v8.9.3
default -> v8.9.3
node -> stable (-> v8.9.3) (default)
stable -> 8.9 (-> v8.9.3) (default)
iojs -> N/A (default)
lts/* -> lts/carbon (-> v8.9.3)
lts/argon -> v4.8.7 (-> N/A)
lts/boron -> v6.12.2 (-> N/A)
lts/carbon -> v8.9.3
anyone have any ideas? I really want this role to be idempotent, and need to figure this, if anyone has any ideas, I'd love to hear 'em ;)
Jordan Harband
@ljharb
@willwh nvm alias default will print it out directly
@willwh however i think the issue might be that terminal colors are messing it up. try TERM=dumb nvm alias default
(that shuts off the colors)
William Hetherington
@willwh
welp, that's pretty awful
thank you so much for the help @ljharb :)
that sorted me right out!
that should probably make it in the Readme.md want a PR?
;)
Jordan Harband
@ljharb
sure, you mean like a general section about terminal colors?
also that nvm alias x prints out what "x" is :-)
nvm --help should also probably say those things if it doesn't already
@willwh a PR would be great :-)
William Hetherington
@willwh
@ljharb groovy, am at work right now, with deadlines, I promise I will crank something out over the weekend though
:)
Jordan Harband
@ljharb
sounds great
William Hetherington
@willwh
thanks so much, again! :)
I made myself a reminder ;) creationix/nvm#1693
jimmy · YIN
@jimmyYSY
hey how to use nvm for windows
Jordan Harband
@ljharb
@jimmyYSY nvm only works on windows if you're using the linux subsystem
jimmy · YIN
@jimmyYSY
@ljharb sorry I don't quite understand
Jordan Harband
@ljharb
@jimmyYSY windows 10 has a thing called "BashOnWindows", or "the linux subsystem", which gives you a unix-like command line interface. that's required to run nvm on windows; otherwise you'll need a different software projecct.
jimmy · YIN
@jimmyYSY
@ljharb ok thanks i will try again
Ricardo Oliveira
@rgoliveira
Does nvim run OK on Windows' bash? I joined a company to work with C# after a long time away from Windows, so I'm not sure if it's worth the trouble trying to use nvim on it
Jordan Harband
@ljharb
it should work fine
Ricardo Oliveira
@rgoliveira
Ok, thanks. I tried out nvim-qt and it's kinda ok for me, but I prefer to use it on the terminal
Oh, crap, I thought I had joined neovim's gitter 😂
Jordan Harband
@ljharb
oh lol
you said nvim, not nvm. yeah no idea about neovim
cswl
@cswl
How do I update node.js install... there doesnt seem to be a update command
Jordan Harband
@ljharb
@cswl there's not. nvm is for managing multiple versions, so if you need a different one, you just install it
cswl
@cswl
Just installing the version like nvm install lts or node does fetch the latest one.. while it doesnt uninstal the older version... kinda tedious I guess I will write a script for it..
Jordan Harband
@ljharb
@mukhtorov this channel is for nvm, not react.
Sardor
@mukhtorov
ah, sorry
Alibra
@thedubb
Hopefully someone can help me with an nvm issue I'm having. I'm currently using node version 10.5 but anytime I globally install an npm package, it installs to a 9.4.0 directory .../.nvm/versions/node/v9.4.0. I can't seem to figure out how to get nvm to install to the directory that I'm currently in. Is there a command I can run for this?
Jordan Harband
@ljharb
@thedubb what does nvm current print out, and npm root -g?
sameeroath
@sameeroath
Screenshot 2019-02-27 09.45.18.png
Hi guys, can someone please check above image as to why it's happening :/
shouldn't require('<global package name>') just work for me? if yes, can someone please guide me thru steps to fix this.
Jordan Harband
@ljharb
@sameeroath no, global packages are never requireable
things you require are dependencies - thus they must be in your package.json and locally installed.