Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    TJ Egan
    @tw15egan
    👋
    Audrey Moon
    @lovemecomputer
    hello everyone!
    DAK
    @dakahn
    🧛🏽‍♂️Hi!
    Josh Black
    @joshblack
    👋
    Julian
    @julzmon
    Suuuup
    DAK
    @dakahn
    Hello all!
    So far we've got a preeetty welcoming community here. I like it.
    Audrey Moon
    @lovemecomputer
    way better than myspace
    DAK
    @dakahn
    🚀 👋🏽
    Kimberly Andersson
    @kimberlyandersson
    Hi!
    Josh Black
    @joshblack
    Hi @kimberlyandersson ! 👋
    hshockley
    @hshockley
    2019-07-05 10_30_03-hshockley@wal-l-hs02_ _mnt_c_Users_hshockley_Desktop_Rocket Carbon_carbon.png
    Hello, getting this error when building through WSL. Still able to run storybook on the react package but unsure what is causing this:
    DAK
    @dakahn
    Hi! 👋🏽 Could you post more of your terminal output here?
    @hshockley
    Also is this a fresh clone -- or one that was previously accessed by a Windows non-WSL environment?
    hshockley
    @hshockley
    Just got a fresh clone and I am getting the same error. I also had troubles with yarn install as it was having access errors or failing to see modules that were there.
    DAK
    @dakahn
    Can you post a little more of your terminal output here so I can help debug?
    hshockley
    @hshockley
    2019-07-09 14_37_57-hshockley@wal-l-hs02_ _mnt_c_Users_hshockley_Desktop_RocketCarbon2_carbon.png
    2019-07-09 14_37_07-hshockley@wal-l-hs02_ _mnt_c_Users_hshockley_Desktop_RocketCarbon2_carbon.png
    DAK
    @dakahn
    This output is during the yarn install or yarn build step?
    is this the errors from install?
    hshockley
    @hshockley
    Those errors are from yarn install
    The first screenshot I posted is from yarn build
    DAK
    @dakahn
    can you post the whole output -- specifically I want to see the command you're running and from what directory its running in 👍🏽
    hshockley
    @hshockley
    2019-07-09 14_49_13-Window.png
    2019-07-09 14_50_33-Photos.png
    2019-07-09 14_51_03-hshockley@wal-l-hs02_ _mnt_c_Users_hshockley_Desktop_RocketCarbon2_carbon.png
    DAK
    @dakahn
    but that's after a yarn install with errors, right?
    going through our install steps on my WSL env now
    hshockley
    @hshockley
    Yeah, it's after a yarn install with errors. Tried npm i and then sudo npm i which seemed to work without producing any errors.
    DAK
    @dakahn
    the sudo npm is probably where you're getting permission issues. this project requires Yarn. We use Yarn Workspaces to manage dependencies between the repos
    hshockley
    @hshockley
    sudo npm was used after getting errors with yarn install but I will start over again and report back
    DAK
    @dakahn
    Okay cool!
    post the output of yarn install when you get there 👍🏽
    hshockley
    @hshockley
    2019-07-09 15_15_30-hshockley@wal-l-hs02_ _mnt_c_Users_hshockley_Desktop_RocketCarbon2_carbon.png
    DAK
    @dakahn
    Okay a few more questions :smile:
    Are you using Ubuntu in WSL or a diff distro?
    hshockley
    @hshockley
    Ubuntu in WSL
    DAK
    @dakahn
    Great. And did you install Yarn using the recommended method via curl here:
    https://yarnpkg.com/en/docs/install#debian-stable
    That error being thrown it seems comes from Yarn trying to access a private package -- usually weird pathing or a faulty install can cause something like this
    hshockley
    @hshockley
    Used sudo apt install yarn
    DAK
    @dakahn
    ah, okay
    Are you willing to try installation via their recommended method -- it seems to add their package repository which would insure theres not versioning conflicts
    My guess off the top of my head is that you can't access some aspect of your Yarn installation (installed with super user permissions)
    hshockley
    @hshockley
    Yes. Seems like a permissions issue as sudo npm i was able to install the packages without error.
    DAK
    @dakahn
    WSL was weird for me to wrap my head around. I remember I followed Dave Rupert's excellent guide for an initial setup:
    https://daverupert.com/2018/04/developing-on-windows-with-wsl-and-visual-studio-code/
    Which has a cool rundown on how it works and how the Windows file system interacts with WSL :smile_cat:
    DAK
    @dakahn
    I'll be hanging out for the rest of the afternoon @hshockley -- looking forward to getting you up and running :muscle:
    hshockley
    @hshockley
    Yeah, I'll try that guide. Thanks for the help DA.