Tools: Hard link for test-fixture dependency

[nvangiessel]

Please publish a working version of test-fixture in npm, and depend on that in wct. Because the github fallback can't be reached in our environment as our CI containers have no internet connection for security reasons, but they have a connection to a NPM proxy.

dependency:
[email protected] (git://github.com/polymerelements/test-fixture.git#05514d6f32ade6fe54de5b242bbb43ea9dcff3c0)

[wilmveel]

We are facing the same problem. Trying to install web-component-tester behind a proxy. It seems not to work because of this issue.

[Bubbit]

Is there a reason why the dependency on test-fixture is set with a short-hand resolver and not set on a specific version?

I'm aware you can set a proxy for npm to get these packages, but some companies are very strict and don't allow this.

Npm chose to make it impossible to create your own custom shorthand resolver like bower does so rerouting it to your internal npm registry is impossible in this case.

[justinfagnani]

The @polymer scoped packages were published as part of an experiment to see what we need to do to sustainably publish working npm packages. They're not ready for use yet.

test-fixture just happens to work (sometimes) because it doesn't have any dependencies itself and it's a direct dependency of wct and probably usually ends up being installed at the top-level of node_modules/. I don't want to make an exception for test-fixture and update it without also updating the other packages, because that will lead to even more confusion, and unfortunately we're just not ready to keep all the @polymer npm packages up to date without more tooling on our side.

test-fixture really should be coming in from Bower, with the web-component-tester Bower package.

[justinfagnani]

If anyone's curious about the backstory behind the npm packages, and have the time, here's the issue where we discussed the options that lead to that experiment: https://github.com/Polymer/polymer/issues/326

[Bubbit]

@justinfagnani That isn't a fix atm, the issue is that by installing WCT or just the Polymer-cli for that matter it internally uses the scoped package, it's not something we as users try to force, it's the other way around we don't want to use the scoped ones for now (due to proxy problems)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.