Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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.
    Kimberly Andersson
    @kimberlyandersson
    we've got four people hitting errors in building the monorepo today (wsl and mac). it's failing on yarn install (for those on wsl) or "succeeding" without actually installing any of the node modules in the Elements packages and then failing on yarn build (on mac).
    any ideas what might be going on?
    TJ Egan
    @tw15egan
    If you're trying to load the monorepo locally, you should just need to run yarn then yarn build at the top level
    Let me spin up a new clone and verify it's working on my end
    DAK
    @dakahn
    yarn install specifically right, @tw15egan
    doesn't that do a few extra things (clear cache etc)
    TJ Egan
    @tw15egan
    I always just run yarn
    DAK
    @dakahn
    oh
    Kimberly Andersson
    @kimberlyandersson
    tried that
    there's no content in the node modules folders of colors, icons, grid, layout, motion, themes, or type
    totally empty after yarn install
    DAK
    @dakahn
    just so we're all on the same page @kimberlyandersson you're team is following these docs?
    https://github.com/carbon-design-system/carbon/blob/master/docs/developing.md
    TJ Egan
    @tw15egan
    Also, FYI Running yarn with no command will run yarn install, passing through any provided flags so same thing :D
    Kimberly Andersson
    @kimberlyandersson
    yep
    TJ Egan
    @tw15egan
    Which version of node are y'all on?
    Kimberly Andersson
    @kimberlyandersson
    we've tried 10.16 and 10.15
    DAK
    @dakahn
    doing a fresh clone, install, and build on my WSL Ubuntu env here now
    TJ Egan
    @tw15egan
    I'm testing on my mac env
    Kimberly Andersson
    @kimberlyandersson
    thanks!
    also may be worth noting that we've tried on both https://github.com/carbon-design-system/carbon and our fork https://github.com/RocketSoftware/carbon , same errors
    DAK
    @dakahn
    i'll test your fork after I verify our master
    TJ Egan
    @tw15egan
    So yeah, it's installing @carbon/colors at the top level, but its not installing any of the dependencies inside of packages/colors in that packages node_modules
    But I'm not getting errors on yarn build
    DAK
    @dakahn
    @kimberlyandersson can you check your Yarn version for me?
    Kimberly Andersson
    @kimberlyandersson
    1.16
    DAK
    @dakahn
    :thumbsup:
    Josh Black
    @joshblack
    What are the errors that you all are seeing? (sorry, just catching up!)
    DAK
    @dakahn
    okay, that successfully installed and built on Windows 10, WSL Ubuntu with latest yarn and Node 10.16