<p>Looks like you haven't submitted your plugin repo to <a href="https://packagist.org/" rel="nofollow noreferrer">Packagist</a> yet. You'll need to do that before it's available via Composer (<a href="https://docs.craftcms.com/v3/extend/plugin-guide.html#packagist" rel="nofollow noreferrer">per the docs</a>).</p>

<hr>

<p><strong><em>Update and additional info:</em></strong>
Like you mentioned in the comments, and like it's mentioned in the docs (see the <a href="https://docs.craftcms.com/v3/extend/plugin-store.html#submit-for-approval" rel="nofollow noreferrer">Tip box here</a>), Packagist is optional for your Craft plugin. You can totally add your plugin to the plugin store and install it via the plugin store without ever putting it on Packagist. If you use Craft's <code>Update</code> button in the dashboard, everything will work like you'd expect. The reason is because Craft is using its own logic (relying on Craftnet) to resolve packages. However, once you switch to running composer commands in the CLI to do your updating/installing/whatever, those packages won't be found (because they don't exist on Packagist yet) and Composer is obviously not using Craftnet's logic.</p>

<p>So if you want to be able to install/update your plugin via Composer, I'd recommend adding your plugin to Packagist. It honestly doesn't take that long (like 2 min maybe) and it will save you from quite a few support tickets down the road of people using Composer and having issues with your plugin's "absence".</p>

CC BY-SA 4.0
2019-03-12T19:43:11.153Z
Wow. For some reason I read that part of the docs as an optional. Thanks (:
peirix
CC BY-SA 4.0
2019-03-13T00:42:21.160Z
Ben (from Pixel&Tonic) actually gave me some more info on this over in Discord after I answered the question, so I'll update my answer with some better info on "why". tldr; yes, it actually is optional...
Jalen Davenport
CC BY-SA 4.0
2019-03-12T14:43:20.123Z
2019-03-13T00:51:40.970Z
2019-03-13T00:51:40.970Z
Jalen Davenport
<p>I've made a plugin, that I'm now trying to include in a live project, but when I try to install it via the plugin installer, I get a 500 error, and if I try to include it using composer, I get the following error:</p>

<pre><code>$ composer require mustasj/expanded-search
[InvalidArgumentException] Could not find a matching version of
package mustasj/expanded-search. Check the package spelling, your
version constraint and that the package is available in a stability
which matches your minimum-stability (stable).
</code></pre>

<p>I've set the version to 1.0.1 in GitHub: <a href="https://github.com/mustasj/expanded-search/releases" rel="nofollow noreferrer">https://github.com/mustasj/expanded-search/releases</a></p>

<plugin-development>
How to set stability version in plugins?
# How to set stability version in plugins?

(Asked by: username_0 on 2019-03-12)

I've made a plugin, that I'm now trying to include in a live project, but when I try to install it via the plugin installer, I get a 500 error, and if I try to include it using composer, I get the following error:
$ composer require mustasj/expanded-search
[InvalidArgumentException] Could not find a matching version of
package mustasj/expanded-search. Check the package spelling, your
version constraint and that the package is available in a stability
which matches your minimum-stability (stable).

I've set the version to 1.0.1 in GitHub: https://github.com/mustasj/expanded-search/releases

**Tags:** plugin-development

---

## 1 answers

### Answer by username_1 on 2019-03-12. Score: 2 | Accepted answer

Looks like you haven't submitted your plugin repo to [Packagist](https://packagist.org/) yet. You'll need to do that before it's available via Composer ([per the docs](https://docs.craftcms.com/v3/extend/plugin-guide.html#packagist)).

---

***Update and additional info:***
Like you mentioned in the comments, and like it's mentioned in the docs (see the [Tip box here](https://docs.craftcms.com/v3/extend/plugin-store.html#submit-for-approval)), Packagist is optional for your Craft plugin. You can totally add your plugin to the plugin store and install it via the plugin store without ever putting it on Packagist. If you use Craft's `Update` button in the dashboard, everything will work like you'd expect. The reason is because Craft is using its own logic (relying on Craftnet) to resolve packages. However, once you switch to running composer commands in the CLI to do your updating/installing/whatever, those packages won't be found (because they don't exist on Packagist yet) and Composer is obviously not using Craftnet's logic.

So if you want to be able to install/update your plugin via Composer, I'd recommend adding your plugin to Packagist. It honestly doesn't take that long (like 2 min maybe) and it will save you from quite a few support tickets down the road of people using Composer and having issues with your plugin's "absence".

> **Comments:**
> **username_0**: Wow. For some reason I read that part of the docs as an optional. Thanks (:  
> **username_1**: Ben (from Pixel&Tonic) actually gave me some more info on this over in Discord after I answered the question, so I'll update my answer with some better info on "why". tldr; yes, it actually is optional...  

---

