Introduce Webpack

[nizniz187]

Use Webpack as the project build tool

[nizniz187]

ES Module export support is still an experimental feature, which is very basic and unstable.
Reference:

• Latest release (last month)
• Issue thread

---

As the merits we expect this WC library we are building on should bear with --modern, light, and flexible-- we should re-consider if we are going to use Webpack as the bundling tool.

To sum up, the main reasons why we want to introduce Webpack are:

1. To bundle with 3rd-party libraries for some of our component features, such as code highlighting. (Add Basic Component - Code #17)
2. To solve the problem of component load delay. (Solve Loading Delay Problem #34)

And the options we have now are:

1. Keep using Webpack with common js library export.
   • Can solve the library bundling. (CSS import remains a problem though.)
   • Cannot solve the delay problem, since we still need to load wc package AFTER DOM loaded.
   • The whole wc package can only be bundled & imported as a whole due to the limit of common js model.
   • Reference:
     • Author Libraries
2. Use other bundling tool which supports ES module bundling, like rollup.
   • Could give a try, despite rollup have some bad reviews.
3. Use only self-managed modules, ie. manage 3rd-party libraries on our own.
   • Support ES module libraries only.
   • CSS import remains a problem.
4. Use no dependency module, ie. re-build all wheels on our own.

[nizniz187]

Conclusion of weekly meeting No. 5: choose 3. Use only self-managed modules, ie. manage 3rd-party libraries on our own.