Closed hidai closed 6 years ago
keanulee
commented
6 years ago We're in the progress of releasing 3.x versions of our elements to NPM, and part of that change is adding NPM support to webcomponents.org. The 0.0.4 release is the latest non-prerelease version on NPM - 3.0.0-pre.19 is the latest prerelease version which we hope to release soon (demo is broken on webcomponents.org because the README demo hasn't been updated for 3.x). Please bear with us during this transition.
hidai
commented
6 years ago I see. But we're still using Polymer 2 and can't pay resources for migration of 3.x shortly. Webcomponents.org is important tool for us to see specs and demos before using components. I think it should serve 2.x contents as well for the most Polymer developers who are still using 2.x. Is it difficult to take 2.x pages back to see specs and demos?
masonlouchart
commented
6 years ago Please, publish the v2.1.1 on NPM, it starts to be ridiculous. If it's so difficult to publish on NPM stop use it. Sorry for my fucking feeling but I'm using Polymer since the v0.5 and now I feel like the Polymer Team thrown everything to join the JS community. You could have at least avoid regression.
keanulee
commented
6 years ago We are not planning to publish 2.x versions of elements on NPM, one technical reason (among others) being NPM doesn't guarantee flat installation that HTML imports needs. 3.x elements will use ES modules with package names instead.
hidai
commented
6 years ago Just realized that there is a "View Bower docs" link on the page. This is what I wanted. Closing.
masonlouchart
commented
6 years ago Completely understandable @keanulee.
Nice catch @hidai さん! 👍
Description
Seems like the paper-button page is broken, but other elements are ok.
Expected outcome
Actual outcome
Live Demo
https://www.webcomponents.org/element/@polymer/paper-button https://www.webcomponents.org/element/PolymerElements/paper-button
Steps to reproduce
Browsers Affected
I only tested on Chrome OS 66.