Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    Kimberly Andersson
    @kimberlyandersson
    I don't have everyone in front of me right now, but it's been a combination of files NOT FOUND with the windows folks and on mac, elements packages as "micromatch.matcher(): pattern should be a string, regex, or function."
    we also tried npm at some point and hit ETARGET npm ERR! notarget No matching version found for eslint-config-carbon@10.3.0
    Josh Black
    @joshblack
    For the second error, that totally makes sense. The project itself uses Yarn Workspaces and that means we can rely on internal packages that may not be published. NPM wouldn't know about those so it tries to fetch from the live registry and can't find them.
    Kimberly Andersson
    @kimberlyandersson
    yea, we let that method go quickly
    Josh Black
    @joshblack
    haha
    Unfortunately, the Windows error is totally known and is possibly related to that mac error in the sense that the patterns aren't working
    I'm curious if it's a shell thing now given that our patterns are things like scss/*.scss
    Also, sorry this has been such a headache setting this up!
    DAK
    @dakahn
    Well they're Windows by way of WSL running Ubuntu -- which is what I just successfully built with
    Josh Black
    @joshblack
    This has become such a thing 😭
    Kimberly Andersson
    @kimberlyandersson
    it's an awesome third day for my newest intern haha
    DAK
    @dakahn
    I have that right, right @kimberlyandersson?
    Josh Black
    @joshblack
    Ugh, I bet. On the Mac side, are they using the stock Terminal.app ?
    Kimberly Andersson
    @kimberlyandersson
    @dakahn - what directory did you clone the project into?
    Josh Black
    @joshblack
    We recently had an intern join who went through setting things up, but I think she is using iTerm.
    Kimberly Andersson
    @kimberlyandersson
    yep. (it's only me on mac)
    Josh Black
    @joshblack
    Perfect 👌 Let me play around with that then and see what's going on. DA has the WSL support covered I think 🙂
    DAK
    @dakahn
    I cloned into a directory on my Windows OS. Specifically a folder called projects.
    Then from a terminal for WSL Ubuntu I cd into that folder and run the subsequent commands
    Kimberly Andersson
    @kimberlyandersson
    like through /mnt/c/...?
    DAK
    @dakahn
    Exactly!
    if I type pwd in my terminal the output for my root is /mnt/c/Users/{username}
    This is weird, I know. The section in this article called "FAQ: Where do my project files live?" explains this relationship really well
    hshockley
    @hshockley
    Hey @dakahn, installing in /mnt/c/Users/.../Desktop gives me an error that node-gyp can't find the python executable on my path, even though it is on my path through checking echo $PATH and windows env variables
    Whats the output of echo $PATH for you?
    DAK
    @dakahn
    Are you using Node for Windows? Or Node installed in WSL Ubuntu (or the like)
    hshockley
    @hshockley
    Node installed in WSL Ubuntu
    10.15
    DAK
    @dakahn
    In my root
    /home/{username}/.nvm/versions/node/v10.16.0/bin
    among a host of other things
    hshockley
    @hshockley
    10.15.3 which is the one I am currently using through nvm and 10.16
    DAK
    @dakahn
    Either v10 should be okay, can you post your terminal output -- specifically that python error you talked about before?
    DAK
    @dakahn
    also -- what's the output of running python -V
    (capital V)
    hshockley
    @hshockley
    Python 2.7.15rc1