(node:13772) [DEP0148] DeprecationWarning about frontend-webpack-boilerplate HOT 3 CLOSED

Hi @mityaua

This deprecation warning will not prevent the template from proper building your assets.
As far as I can see the warning is generated from the postcss here is the issue discussing this warning with different versions of node DeprecationWarning: Use of deprecated folder mapping.

from frontend-webpack-boilerplate.

@mityaua

Images part of the content (<img> tags and files placed under src/images/content) are not part of the design of the page and does not go through optimisation as the assumption here is that they have been uploaded via CMS or something similar, like they are dynamic generated images - published in "runtime" etc.

All images part of the design itself (CSS backgrounds, etc.) are being optimised during the "build" assets process.

This is the default behaviour, you can change directory names or reconfigure if you want to optimise the content images if you build a fully static templates that are not targeted to be embedded in a server side web application.

from frontend-webpack-boilerplate.

Yes, indeed, your "plate" works without errors, only this notification. Updating node to version 15.10 solves this problem.

Does this mean that the next warning has nothing to do with this? Or am I doing something wrong with the pictures?

I just put image in the src/images folder and then npm run production (or npm run build). Compression not working? File size has not changed.

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (500 KiB).
This can impact web performance.
Assets:
images/content/everest_mountain.jpg (3.03 MiB)

WARNING in webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

webpack 5.22.0 compiled with 2 warnings in 22824 ms

from frontend-webpack-boilerplate.