title: Is there a way to specify different paths for the same dependencies in package.json?
body: <p>I am working on an npm package that includes an <code>example</code> directory to run/test the actual package. In the <code>example</code> directory, I have included back the parent package using <code>&quot;file:..&quot;</code>.</p>
  <p>This works fine when developing and making frequent changes to the parent package, but if I want to use the <code>example</code> as a stand-alone app, I would need to point to the actual npm package.</p>
  <p>Is there a way to have &quot;2 configs&quot; in the same <code>package.json</code>:</p>
  <ul>
  <li>one that points to `&quot;file:..&quot; for local development</li>
  <li>one that points to the npm package to use as a stand-alone app</li>
  </ul>
  <p>This would avoid duplicating the <code>example</code> directory</p>