Answers.Body: <p>I had a similar issue yesterday.</p>
  
  <p>When running composer install from my linux (Homestead box), via the command line, a stack of weird errors flew by indicating a "problem with the zip file".</p>
  
  <p>Then craft died. All the vendor/craftcms files were created but empty!</p>
  
  <p>Only way round it, for me, was to run the composer install from windows instead. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-04-25T11:33:43.343Z
Answers.Text: strange… I didn't changed anything in the config file. Could it be that version 3.1.23 has a bug?
Answers.UserDisplayName: Samuel
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-04-26T12:02:18.403Z
Answers.Text: Maybe - or perhaps something weird with the zip file maybe?
Answers.UserDisplayName: sunscreem
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-04-26T13:01:19.017Z
Answers.Text: an official answer would be nice. atm I can't update my plugins or install a new one. If I try it craft totally crash.
Answers.UserDisplayName: Samuel
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-04-25T11:19:03.077Z
Answers.LastActivityDate: 2019-04-25T11:19:03.077Z
Answers.UserDisplayName: sunscreem
Answers.Body: <p>I fixed this locally. </p>
  
  <p>I had to clear my composer cache with <code>composer clear-cache</code>. Composer install ran perfectly and all is well with the world.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-04-30T18:19:17.217Z
Answers.LastActivityDate: 2019-04-30T18:19:17.217Z
Answers.UserDisplayName: sunscreem
Body: <p>I was on version 3.1.22. As usual, I wanted to install the update on Craft CMS 3.1.23.
  So I clicked Install and got this error:</p>
  
  <blockquote>
    <p>Status: Error</p>
  </blockquote>
  
  <p>But that was not all ... My complete vendor/craftcms/cms folder has been deleted. The solution to get back to the CP and the frontend, was to manually upload 3.1.22 back to the folder. When I started the update again - same error. In the while, I have manually updated to 3.1.24. However, I can no longer update plugins or install new ones. The CMS folder is deleted every time.</p>
  
  <p>Does anyone have a similar problem or idea how to solve this? Thanks!</p>
  
Tags: <craft3><install><installation><updates>
Title: my vendor/craftcms/cms folder delete automatically after every update or install
ThreadText: # my vendor/craftcms/cms folder delete automatically after every update or install
  
  (Asked by: username_0 on 2019-04-25)
  
  I was on version 3.1.22. As usual, I wanted to install the update on Craft CMS 3.1.23.
  So I clicked Install and got this error:
  
  > Status: Error
  
  But that was not all ... My complete vendor/craftcms/cms folder has been deleted. The solution to get back to the CP and the frontend, was to manually upload 3.1.22 back to the folder. When I started the update again - same error. In the while, I have manually updated to 3.1.24. However, I can no longer update plugins or install new ones. The CMS folder is deleted every time.
  
  Does anyone have a similar problem or idea how to solve this? Thanks!
  
  **Tags:** craft3, install, installation, updates
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-04-25. Score: 1
  
  I had a similar issue yesterday.
  
  When running composer install from my linux (Homestead box), via the command line, a stack of weird errors flew by indicating a "problem with the zip file".
  
  Then craft died. All the vendor/craftcms files were created but empty!
  
  Only way round it, for me, was to run the composer install from windows instead.
  
  > **Comments:**
  > **username_0**: strange… I didn't changed anything in the config file. Could it be that version 3.1.23 has a bug?  
  > **username_1**: Maybe - or perhaps something weird with the zip file maybe?  
  > **username_0**: an official answer would be nice. atm I can't update my plugins or install a new one. If I try it craft totally crash.  
  
  ---
  
  ### Answer by username_1 on 2019-04-30. Score: 1
  
  I fixed this locally.
  
  I had to clear my composer cache with `composer clear-cache`. Composer install ran perfectly and all is well with the world.
  
  
  ---
  
  