Machine: pre: - mkdir -p ~/.yarn-cache environment: RAILS_ENV: test RACK_ENV: test NODE_ENV: test dependencies: override: - nvm install v4.4.6 # default version in image of 0.x.y can't run yarn - nvm alias default v4.4.6 - sudo apt-key adv -keyserver -recv D101F7899D41F3C3 - echo "deb stable main" | sudo tee /etc/apt//yarn.list - sudo apt-get update -qq - sudo apt-get install -y -qq yarn - mkdir -p node_modules & rm -r node_modules/ - yarn install -pure-lockfile # this is the step that hangs cache_directories: - "~/.yarn-cache" The build hangs at this point and eventually circle times out (no output for 10 minutes) and kills the build. Now yarn should be uninstalled.Screen Shot at 9.26.47 PM.png 2176×376 25.7 KB ![]() ![]() Especially when using sudo, you should not blindly copy/paste commands you find on the internet, so type out the below manually. Returns: bash: /home/caleb/.nvm/versions/node/v16.13.2/bin/yarn: No such file or directory Rm -rf ~/.nvm/versions/node/v16.13.2/bin/yarnpkgĭoing yarn now will resolve to /usr/local/bin/yarn so you need to delete that as well. Returns /home/caleb/.nvm/versions/node/v16.13.2/bin/yarnĭelete from nvm rm -rf ~/.nvm/versions/node/v16.13.2/bin/yarn ![]() You're on yarn v3! Find out where it's installed. If your install process looked like: corepack enableĪnd, if you're on Ubuntu (or perhaps similar, I only tested on Ubuntu), then your uninstall process will look like: yarn -version
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |