title: Artifactory scoped npm packages have extra "scope" in path
body: <p>I have published a scoped npm package in an npm-local repo on Artifactory.  For example let's say it's @scope/packagename in the package.json.  The path it creates on Artifactory seems to have an extra @scope in the path: <code>https://artifacts.company.com/artifactory/webapp/#/artifacts/browse/tree/General/npm-local/@scope/packagename/-/@scope/packagename-version.tgz</code></p>
  
  <p>Is this correct? Is there a problem with the publish? This is related to another question: <a href="https://stackoverflow.com/questions/40870241/installing-scoped-npm-packages-from-artifactory">Installing scoped npm packages from Artifactory</a>.  When I try to install this package I just published I get a 404 error leading me to believe there might be something wrong with the path?</p>
  
  <p>Edit:
  To publish my scoped package I edited my .npmrc:</p>
  
  <pre><code>@scope:registry=https://artifacts.company.com/artifactory/api/npm/npm-local/
  //artifacts.company.com/artifactory/api/npm/npm-local/:_password=Q......
  //artifacts.company.com/artifactory/api/npm/npm-local/:username=dgriner
  //artifacts.company.com/artifactory/api/npm/npm-local/:email=d.griner@company.com
  //artifacts.company.com/artifactory/api/npm/npm-local/:always-auth=true
  </code></pre>
  
  <p>In my package.json file I have the following:</p>
  
  <pre><code>"name": "@scope/packagename",
  </code></pre>
  
  <p>I then ran <code>npm publish</code> and it created the above path.</p>