The longer title should be: Experiment with Polymer 3.0 Preview — Building a mini card game with Polymer + Typescript + Webpack.
Webpack and Typescript are not necessarily in Polymer but that’s the tools I familiar with and I like Typescript(probably you should give it a try)!
- I have no prior experience using Polymer. I’m blogging this from a
Here is the demo and sourcode:
Being a long time AAV developer (AngularJs, Angular, Vue), I did follow the Polymer news, but didn’t really take a closer look into it(for some reasons) , until last week — duringPolymer Summit 2017, the Polymer team announces two big changes:
Polymer 3.0 preview: npm and ES6 Modules — Polymer Project_While these changes will be significant, we’re committed to making the transition as seamless as possible. The Polymer…_www.polymer-project.org
- Polymer is moving from
Bower to NPM
(with a twist, you need
with a specific configuration).
- Polymer is switching to using
Suddenly, I feel like “it’s time to try it out!” (I always feel the HTML import syntax looks weird). Probably the marketing slogan works too, #useThePlatform sound welcoming :)!
On a serious note, wouldn’t it be good if you can building performant component using the platform? (Polymer is not a framework. It’s a thin sugar layer to use the web-components)
After going through thePolymer 3.0 Preview hands-onpublished by the Polymer team, I found a few things that doesn’t look “normal” for a typical AAV developer (me).
- import statement with
and import directly from
using relative path
— It’s a minimalistic example. However, it’s not how we import in Angular, Vue and React “normally”. It’s the Bower way of import but it’s not how I normally work with modules.
- HTML in JS —
Personally, I prefer to separate the do HTML template unless the it’s so short (
10 lines). Also, with proper syntax highlight.
Therefore, I decide to build a Polymer 3.0 project from scratch with the way I used to.