zmrhaljiri / superdevstack Goto Github PK

Watching files and making certain operations to it (after saving) could be applied also to files that are not specified in entry files or imported by files in the dependency graph.

For example, files in /api folder are not imported (so Webpack does not know about it), but it's still important to lint it on save or while running formatting NPM task.

Discover if it's possible to solve it via Webpack or some plugins. Otherwise it would be needed to implement a task runner and perhaps separate linting from Webpack - that I'd like to avoid.

Implement the loader for responsive images allowing to create multiple images from one with generating srcset. In addition, add some example to the code and also the documentation.

URL: https://github.com/herrstucki/responsive-loader

There are multiple plugins that can be used for JS minification. The top 3 seems to be:

• Terser (https://github.com/terser-js/terser)
• UglifyJS (https://github.com/mishoo/UglifyJS2)
• Babel minify (https://github.com/babel/minify)

Which one should be used for the best assets optimization? Compilation speed is priority number 2, of course if it would not be dramatically slower.

Some explanation: https://stackoverflow.com/questions/52661999/babel-minify-vs-terser-instead-uglify-js

Implement the loader for loading/extracting SVGs into a sprite file. In addition, add some example to the code and also the documentation.

URL: https://github.com/TodayTix/svg-sprite-webpack-plugin

The NPM script copy.externals is used to copy files from externals/ folder into the dist/ folder.

Currently, due Webpack plugin is cleaning the dist folder automatically before compilation, it's needed to exclude the externals/ folder from the plugin configuration + specify the task as a separate NPM script that's run before the NPM webpack script.

A suggestion is to use the copy task as a Webpack hook, after each compilation. More specifically, after the dist/ folder is cleaned up, copy the external files there.

The WebpackAutoInject plugin is increasing the version property in package.json.

There are 3 available options, each increasing different number:

• Major - from 1.0.0 to 2.0.0
• Minor - from 1.0.0 to 1.1.0
• Patch - from 1.0.0 to 1.0.1

Currently, every time build is run, it increases the version by 1 (patch option).

Suggestion is to create an argument to the build script that would apply the specified option. Also with letting patch to by the default option.

Examples:
npm start build - default, for patch change
npm start build --env.minor - for minor change
npm start build --env.major - for major change

Add the cache-loader plugin for caching an expensive loaders.

A proper analysis must be done, see the note from the loader documentation:

Note that there is an overhead for saving the reading and saving the cache file, so only use this loader to cache expensive loaders.

URL: https://github.com/webpack-contrib/cache-loader