Skip to content

Milestones

List view

  • When building a project, it may contain several modules whose won't change during the project development. This fact deals with the use of caching for modules and files what won't change, in order to accelerate the building process https://webpack.js.org/configuration/resolve/#resolveunsafecache

    No due date
  • It is useful for the growth of any project to leave behind those times when building just for testing. Those times may rather become past ones, as the current present gives us tools and techniques such a development server, provided by webpack, and a hot module replacement system. Web development may be setup and hot module replacement further configured.

    No due date
    0/2 issues closed
  • We need to speed up out site, by preloading external dependencies, Use plugins such to preload fonts and libraries such Vue or Roboto On the other hand, do the same using dynamic import magic comments ## Resources - https://github.com/GoogleChromeLabs/preload-webpack-plugin - https://medium.com/webpack/link-rel-prefetch-preload-in-webpack-51a52358f84c - https://medium.com/front-end-weekly/webpack-and-dynamic-imports-doing-it-right-72549ff49234 - https://blog.jakoblind.no/speed-up-site/

    No due date
    0/1 issues closed
  • Somehow, our application may import modules (what could be components, images or JSON data files) dynamically (with its matching babel polyfill) and using prefetch order number to prioritize those chunks we should need to be first in the dynamic loading queue. We also want to use webpackMode for choosing destination chunks: one chunk for many modules (lazy-once), parent chunk (eager) or module's own chunk (lazy). By using webpackChunkName we will set names to chunks rather than letting webpack assigning just numbers.

    No due date
    0/2 issues closed