search

PolymerElements / test-fixture

21 stars 14 forks source link

NPM package name conflict #28

Closed BenoitPerrot closed 8 years ago

BenoitPerrot commented 8 years ago

Hello,

A different npm package having the same name (ie test-fixture) is already registered on npmjs.org. This is somewhat problematic, as it makes the getting of slightly more difficult: the only way to get the npm package is to point at it via a git url. This is generally fine but in some environment , it is desirable to avoid accessing git repositories and instead rely on some caching proxy (eg nexus), and for that the origin point (npmjs site) must host the "expected package". As another yet minor issue, the dependency information on npmjs site is also gotten wrong (web-component-tester is said to use the other, "wrong" test-fixture).

I realize how difficult it can be to change the name of the package, so probably another solution should be devised (having the other package removed, as not having been updated for 2 years, etc.) - I just wanted you to know about the issue, and see if you could devise a solution.

justinfagnani commented 8 years ago

we'll register this as @polymer/test-fixture

justinfagnani commented 8 years ago

Sorry, it was already published here: https://www.npmjs.com/package/@polymer/test-fixture

We'll work on updating to the real version numbers soon.

BenoitPerrot commented 8 years ago

Thanks!

When done, I will propose a patch for Polymer/web-component-tester to have its package.json file points to @polymer/test-fixture v1.0.0.