Branching for Polymer 2 - Webpack - PostCSS about polymer-skeleton HOT 8 CLOSED

What about upgrading everything to Polymer 2 now as first thing todo?
I think we should NOT cover IE11, so we can also avoid transpilation with babel. Also we may need to rework something about webpack, but we haven't yet a build process, so could be great work on it with the new Polymer version.
cc: @equinusocio

from polymer-skeleton.

I agree. There is no problems about the rc release? I mean breaking changes before the final release..

from polymer-skeleton.

RC will not have breaking changes, but if will have some, I think will be small changes, so no problems!

We can close a bunch of issues before pushing the branch to the master.

from polymer-skeleton.

So we need to switch from Webpack to Polymer-cli. Related #6.

Also we need to integrate the polymer serve withpostcss and browser-sync (basically with our dev command).

Another thing could be to think about the folder structure as ferrety proposed with:

• main-app.js
• main-app.tpl.html
• main-app.postcss
• view.html (or main-app.html)

from polymer-skeleton.

I will be back on this and other issues this week end.

from polymer-skeleton.

Proposal (just thinking):

• main-app.html
• main-app.postcss

During the development process the .postcss and the .html will be watched.
When .postcss is modified, the content is transpiled and is putted within the .html.

As we will not use webpack we can try to use the new <script type="module"> instead.

from polymer-skeleton.

New, definitive branch related: https://github.com/PolymerX/polymer-skeleton/tree/wp-polymer-2

from polymer-skeleton.

Invalid. Refer #29 for Polymer 3.

from polymer-skeleton.