Migrate to `webpack`

We are currently using rollup for bundling. Though we never faced a major issue with it, rollup is built for libraries which are node focuses not the browser. We will be using rollup for our CLI project but as docsify is browser library, I would prefer to migrate to webpack like its always recommended to use webpack for browser code.

[jhildenbiddle]

The general advise for people asking “rollup or webpack?” has been use to use rollup for distributable packages (browser and/or node) and webpack for applications. This advise was given early on mostly due to webpack v2’s inability to output ES6 modules, but it largely holds true today as rollup is typically faster and produces smaller bundle sizes while webpack tends to be more flexible for app-specific use cases like code splitting. Given this advise and without any other information or preferences to consider, Rollup would typically be the first choice for a distributed bundle like docsify’s.

My preference would be to 1) lower the priority of this task in favor of user-facing issues and 2) commit only to exploring webpack as an option if/when time allows or the need presents itself. Once we have separate webpack and rollup builds available we can compare build time, bundle size, learning curve, features, concerns, etc.

[trusktr]

I don’t think we need to switch to Rollup. We learnt about the caveat (it treats missing dependencies as warnings), so now we know. And now we also have a tests in place to catch missing dependencies once I get a second review so I can merge #1189.

Also, we can add this config to Rollup to throw an error instead of a warning: https://github.com/rollup/rollup/issues/1906#issuecomment-561055996

I think we should close this, as we don’t have a need to convert to Webpack. Let’s re-open this if/when someone needs to convert to Webpack for some reason.

Let’s focus on features/improvements.