These are chat archives for jescalan/roots

23rd
Feb 2017
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 18:29
Hi Jeff, I have a question about a roots bug I am running into
I have installed roots successfully into my packages, but when I do "roots watch", I get an error "-bash: roots: command not found"
Any clues as to why?
Jeff Escalante
@jescalan
Feb 23 2017 18:51
npm i roots -g
you need a global install to get the command
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 18:51
Hey Jeff, I ran that command and still get the same prompt
Roots installs correctly
npm version: 4.1.2
node version: v7.6.0
Screen Shot 2017-02-23 at 10.53.32 AM.png
Jeff Escalante
@jescalan
Feb 23 2017 20:19
ok, so chances are you have an issue with your PATH
is ~/.npm-packages in your $PATH?
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 21:52
No they aren't and I am having trouble setting the correct path
Jeff Escalante
@jescalan
Feb 23 2017 21:56
ok so this is a bash issue and not a roots issue
but i can try to help
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 21:56
I see
Thank you
Jeff Escalante
@jescalan
Feb 23 2017 21:57
what's in your ~/.profile
or ~/.bash_profile
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 21:57
I just reset it and now it is empty
~/.bash_profile
Jeff Escalante
@jescalan
Feb 23 2017 21:58
ok cool, so what did you set up to get your modules installing into .npm-packages
bc this is not the default install location
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:00
I just used Terminal with the basic commands
npm install roots -g
but the location the terminal is pointing to is clearly off and not installing on the correct path
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:09
Just so you know Jeff, I have no .bashrc
but I do have a .bashrc.save
Current file structure:
Screen Shot 2017-02-23 at 2.10.25 PM.png
Jeff Escalante
@jescalan
Feb 23 2017 22:12
ok try this in your bash profile
export PATH="$HOME/.npm-packages:$PATH"
its kind of a long shot
but haha worth a try
you have done something at some point to mess up your npm config
if you run a fresh install, you will not get this issue
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:24
Haha anything is worth a try at this point
Bash_profile is now updated
Started a new terminal
Screen Shot 2017-02-23 at 2.24.38 PM.png
but when I open the terminal at the site folder
its not getting the appropriate roots version at all
Jeff Escalante
@jescalan
Feb 23 2017 22:26
whats the version
what do you get if you type which roots
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:26
I get nothing
blank
Screen Shot 2017-02-23 at 2.25.46 PM.png
Jeff Escalante
@jescalan
Feb 23 2017 22:27
ok that didnt work then
ah Louie, I am really sorry but I don't have time right now to dig deeper :(
i am super busy at work rn
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:27
Ah no worries Jeff
THanks for you help though!
Jeff Escalante
@jescalan
Feb 23 2017 22:27
unfortunately this will be a problem for all node packages
it has nothing to do with roots
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:27
Yeah :(
Thanks for your time Jeff
Jeff Escalante
@jescalan
Feb 23 2017 22:27
if there are any other senior level devs you work with or know
they could work it out if they sat with you
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:28
Yeah, ill ask around
Thanks!
James Dinsdale
@molovo
Feb 23 2017 22:38
I might be wrong, but I think that path should be $HOME/.npm-packages/bin, not $HOME/.npm-packages
Jeff Escalante
@jescalan
Feb 23 2017 22:39
:point_up:
James Dinsdale
@molovo
Feb 23 2017 22:41
If it’s not there, what is the output of find ~/.npm-packages -name roots?
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:53
Hey James
James Dinsdale
@molovo
Feb 23 2017 22:53
Hi :)
Louie Sabado
@LouieSabado_twitter
Feb 23 2017 22:55
James, YOU ARE THE MAN!
That totally worked
Thank you James and Jeff
James Dinsdale
@molovo
Feb 23 2017 22:56
Awesome! Enjoy roots :)
Jeff Escalante
@jescalan
Feb 23 2017 23:54
:raised_hands: