Answers.Body: <p>Although I'm not in favor of the nuclear option in international politics, it works very fine and simply this case. Brad's suggestion of deleting the <code>craft/vendor</code> folder and <code>composer.lock</code> and then running<br>
  <code>composer update</code><br>
  solved the problem immediately. Now I appreciate composer.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-13T00:06:19.753Z
Answers.LastActivityDate: 2018-05-13T00:06:19.753Z
Answers.UserDisplayName: kr37
Body: <p>In updating a plugin for Craft 3, at one point I also renamed it, and at various times did things in the wrong order. At this point, Craft shows the old, unwanted plugin, but</p>
  
  <ul>
  <li>it is not in <code>composer.json</code></li>
  <li>it is not in the <code>craft_plugins</code> table</li>
  <li>none of its tables are in the database</li>
  <li>its files have been deleted from craft/vendor/ns/plugin</li>
  </ul>
  
  <p>On the CP Plugins page, if I click <em>Remove</em>, composer updates and says it is successfully removed, but it still shows up under plugins.</p>
  
  <p>How does Craft still know of its existence? Do I need to put it back into composer to do a <code>composer remove</code>?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-10T16:04:17.647Z
Comments.Text: If it's not in `composer.json`, it may still be in `composer.lock`. Try running `composer update` to make them match.
Comments.UserDisplayName: Lindsey D
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-10T16:55:14.253Z
Comments.Text: Thank you Lindsey. I did that, then tried to remove again. Same results. It acts like it's removing, but the plugin still shows up.
Comments.UserDisplayName: kr37
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-10T18:24:59.780Z
Comments.Text: Weird... if you nuke your `vendor` and `composer.lock` and run `composer update` from the command line does that help?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-11T09:49:18.670Z
Comments.Text: Have you tried clearing / removing the cache?
Comments.UserDisplayName: RvdB
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-12T06:34:00.370Z
Comments.Text: Which cache? I've certainly done Clear Caches from the CP, but I don't think that's what you mean?
Comments.UserDisplayName: kr37
Tags: <plugins><uninstall>
Title: Unable to delete plugin
ThreadText: # Unable to delete plugin
  
  (Asked by: username_0 on 2018-05-10)
  
  In updating a plugin for Craft 3, at one point I also renamed it, and at various times did things in the wrong order. At this point, Craft shows the old, unwanted plugin, but
  
  * it is not in `composer.json`
  * it is not in the `craft_plugins` table
  * none of its tables are in the database
  * its files have been deleted from craft/vendor/ns/plugin
  
  On the CP Plugins page, if I click *Remove*, composer updates and says it is successfully removed, but it still shows up under plugins.
  
  How does Craft still know of its existence? Do I need to put it back into composer to do a `composer remove`?
  
  **Tags:** plugins, uninstall
  
  > **Comments:**
  > **username_1**: If it's not in `composer.json`, it may still be in `composer.lock`. Try running `composer update` to make them match.  
  > **username_0**: Thank you username_1. I did that, then tried to remove again. Same results. It acts like it's removing, but the plugin still shows up.  
  > **username_2**: Weird... if you nuke your `vendor` and `composer.lock` and run `composer update` from the command line does that help?  
  > **username_3**: Have you tried clearing / removing the cache?  
  > **username_0**: Which cache? I've certainly done Clear Caches from the CP, but I don't think that's what you mean?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-05-13. Score: 6 | Accepted answer
  
  Although I'm not in favor of the nuclear option in international politics, it works very fine and simply this case. username_2's suggestion of deleting the `craft/vendor` folder and `composer.lock` and then running  
  `composer update`  
  solved the problem immediately. Now I appreciate composer.
  
  
  ---
  
  