question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Webpack 5 warnings

See original GitHub issue

Hi @fqborges, thank you for the great work. I was wondering if you plan to update this plugin to support Webpack 5. I’m trying to integrate it into some work project and there are some deprecation warnings.

To be more specific:

(node:12688) [DEP_WEBPACK_CHUNK_HAS_ENTRY_MODULE] DeprecationWarning: Chunk.hasEntryModule: Use new ChunkGraph API
(node:12688) [DEP_WEBPACK_CHUNK_ENTRY_MODULE] DeprecationWarning: Chunk.entryModule: Use new ChunkGraph API
(node:12688) [DEP_WEBPACK_MODULE_INDEX] DeprecationWarning: Module.index: Use new ModuleGraph API
(node:12688) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET] DeprecationWarning: chunk.files was changed from Array to Set (using Array method 'filter' is deprecated)

I can help with the upgrade if needed. Let me know and thank you in advance.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:8
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

8reactions
kuworkingcommented, Nov 17, 2020

When using the plugin I see Module.entryModule: Multiple entry modules are not supported by the deprecated API (Use the new ChunkGroup API)

"webpack": "5.4.0",
"webpack-fix-style-only-entries": "^0.6.0",

As suggested, If using https://github.com/webdiscus/webpack-remove-empty-scripts there’s no error and the plugin works

5reactions
webdiscuscommented, Oct 24, 2020

Hi @matteobad, @fqborges I have fixed Webpack 5 deprecation messages (like DEP_WEBPACK_…) and fixed some integration tests. Now all Integration tests pass with Webpack 5.1.3.

See my PR: https://github.com/fqborges/webpack-fix-style-only-entries/pull/41 For usage with Webpack 5 you can try my fork: https://github.com/webdiscus/webpack-remove-empty-scripts

Read more comments on GitHub >

github_iconTop Results From Across the Web

Stats - webpack
Tells stats whether to group modules by their attributes (errors, warnings, assets, optional, orphan, or dependent). module.exports = { //... stats: { ...
Read more >
component-driven/cypress-axe - Warnings with Webpack 5
WARNING in ./node_modules/cypress-axe/dist/index.js 16:47-54 Critical dependency: require function is used in a way in which dependencies ...
Read more >
Webpack 5 - quiet warnings originating from node_modules?
I want to keep warnings from within my own code, but not print warnings if they're caused by code in a node_module. Is...
Read more >
warnings-to-errors-webpack-plugin - npm
Change every warning as error to ensure safe build. Latest version: 2.3.0, last published: a year ago.
Read more >
Webpack 5 Issues | Documentation - Web3Auth
While setting up a new web3 project from scratch, you might face multiple issues with webpack 5. This issue is caused due to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found