title: Npm Including all range of pre-release when defining peer-dependency
body: <p>I am maintaining an NPM package (lets say it as <code>package-A</code>) that relies on an another NPM package(<code>package-B</code>) to function. Therefore, I am in need to add that package as peer-dependency into the <code>package.json</code>, so that npm and the user can be sure that everything is correct.</p>
  <p>The problem is, <code>package-B</code> use pre-release versioning. I am well aware that it uses semver wrong, but I am not able to change the company policy, yet. Meanwhile enforcing to use proper versioning will happen. The semantic is like this:</p>
  <ul>
  <li>1.0.1-alpha.X -&gt; Unstable releases for testing and bleeding edge content</li>
  <li>1.0.1-beta.X -&gt; For every seemingly stable version (like rc)</li>
  <li>1.0.2 -&gt; When the package is production ready.</li>
  </ul>
  <p>So basically, the patch version increases when there is another production release.</p>
  <p><strong>Case:</strong> Because of the versioning, I need to include every package except major one to match as peer dependency, together with pre-releases.</p>
  <p>The need is basically <code>^1.0.0</code> with everything including pre-releases that happens to have <code>1</code> as major as peer dependency</p>
  <ul>
  <li><code>^1.0.0</code> -&gt; Does not include pre-releases</li>
  <li><code>^1.0.0 || &gt;=1.0.0-beta.X</code> -&gt; Does not include e.g. <code>1.0.1-beta.1</code></li>
  <li><code>*</code> -&gt; Does not include pre-releases</li>
  <li><code>^1.0.0 || &gt;=1.X.X-beta.X</code> -&gt; Does not work.</li>
  </ul>
  <p>On semver, there is a parameter called <code>--include-prerelease</code> which I think does what I need, specific to semver commands obviously.</p>
  <p><code>react</code> package on NPM has similar versioning system with proper usage of pre-release. E.g. it has <code>16.0.0</code>, <code>16.0.0-alpha.1</code> and <code>16.6.0-alpha.0</code>. I basically need to include all this on a single range.</p>
  <p><strong>Disclaimer:</strong> Minor version is changed when there is a breaking change going on. Yet again, I am <strong>well aware</strong> that this versioning is not up to semver regulations and advising it unfortunately will not solve the problem at hand.</p>