leogr / dom-deque Goto Github PK

Commit a markdown file - ie. CONTRIBUTING.md - specifying rules for contributions.

All the polymer elements and the polymer library itself are not currently maintained on npm.

Exist a previous attempt to publish polymer and its elements on npm. This test presents cons:

1. It isn't updated
2. Polymer itself and its elements are published as scoped package (nothing wrong) which means that external dependencies - i.e. not scoped packages - e.g., prism library - are installed inside

An easy workaround for issue 2 is to move/copy/link the external packages into the scoped package at post-install time - i.e., node_modules/libx to node_modules/@polymer/libx. This is the solution currently adopted.

But problem 1 remains.

Thus, another solution is to use napa: an helper to install github repos without a package.json file (also npm allows this) with a custom name/path (npm does not allow this).

Cons:

1. This tool can not automatically recursively fetch dependencies.

Which means we have to manually specify all dependencies of our dependencies, and so on.

Conclusions

Both solutions require a post-install hook, so 0 point each.
I choose the second solution since it is desirable to have updatable packages at the (one-time) cost to specify all their dependencies.
Once polymer maintainers will (correctly - i.e., preferably not requiring us to use postinstall script) publish all their libraries plus elements on npm we'll switch back to the natural solution - i.e., solution 1.

I'm implementing it.

Spec here.

I'd like to deprecate che current version (that's just a PoC) then refactor the code in order to make it work with Polymer 2.0.

Issues should be reviewed accordingly.

Setup:

• Travis (with publish from git tag)
• Coveralls
• SauceLabs

Ref.