List view
As explained by Tobias Koppers here https://github.com/webpack/webpack/issues/536#issuecomment-59530883, multiple configuration may lead to produce pre-built _html_ inlined as javascript module default exported strings We can setup a _npm_ task what renders _html_ in files... but it a bit tedious when the amount of _html_ grows. This strategy relies on `html-loader` to work correctly.
No due date•0/1 issues closedOur project needs several html pages rendering the charpters of the manual. This charpters might be produced by just one plugin. Plugins such extract-text-webpack-plugin, which gets text from bundles via an internal loader, allows us to create html pages via entry points. But, because this plugin's loader doesn't process script sources, should be hardened with a customized extra plugin which resolves and loads scripts located in the entries html. On the other hand, there is the static-site-generator-webpack-plugin, what expects javascript entry points what render pages. More over, this plugin allows reducing the website to a single entry point rendering an html with internal links. Static-site-generatorl-webpack-plugin, will crawl those links and generate appropriate output html, by calling the same html. When dealing with this strategy a background router is required in order to select the right content logic for each discovered location; in other words, crawling a "home" html and founding a path such "bout" may imply executing a different logic from that one which created the "home", and that's the place where a router logic is needed. A sample of how to do this is shown in this sample project: https://github.com/pldg/learn-webpack/tree/master/static-site-generator
No due date•0/2 issues closedOur project needs several html pages rendering the charpters of the manual. This charpters might be produced by a plugin used for each charpter. Some useful plugins we may find are html-webpack-plugin which injects selected entry points to the specified template (what may let us output several html files containing webpack bootstrap scripts loading applications rendering content), or web-webpack-plugin, which pursuits a similar goal, but has slightly different config, allowing us to create a website by crawling across a folder, containing folders with page application files, where each folder name is gonna be used as the page name.
No due date•0/3 issues closedWebpack offers the `externals` key in its configuration, in order to list which imports may be ignored by webpack, assuming we will provide an `<script>` way to import them. Furthermore, some plugins, allow to generate manual and automated `<script>` tags, by inflating `html-webpack-plugin` context with those imports detected. These plugins are ones such webpack-cdn-plugin (unofficial and manual), and dynamic-cdn-webpack-plugin (official and automated).
No due date•0/2 issues closedUse `optimization` option in order to split modules, even _javascript_ or _css_. We should use libraries such _bootstrap_ in order to produce a sample subject, because contain both: _javascript_ and _css_ files.
No due date•0/2 issues closedUse _babel_ to transpile code. This will require `babel-loader` for transpiling _javascript_ files and `babel-preset-env` for choosing the desired browsers target.
No due date•0/2 issues closed