Just wrote my own webpack plugin for VueJS.

In serverless application there isn't a good way to pre render a single page web application as there is no server to do this task.

What we can do is use serverside rendering with webpack to locally (or in CI) generate the static HTML markup and include them in a template file like EJS.

In that way, the client browsers would not have to wait for the initial render and the search engines will also be happy.

This feels good! Time to upload it as a npm package 😇

NEVER maintain multiple release branches as a maintainer, period.

Given enough PRs, nobody, not even god-tier maintainers, is able to keep track of all commits and the whole context/story behind it.

Remember that people ALWAYS PR against your master and nobody even cares about your whatever-named-next-branch buried deep inside your feature branches.

Please make it easy for others if you want actual contributions.

Why does every other tool in npm wants to litter their own stupid configuration file at my project root?

So `aws-sdk@^2` happens to include an ancient polyfill `url@0.10.3` which breaks webpack, specifically fork-ts-checker-webpack-plugin, causing it to warn about the inexistence of class "URL".

And this is the default included package for AWS Lambda node.js runtime.

wow, just wow.