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.
Critical Dependencies: the request of a dependency is an expression
See original GitHub issueI got this warning while trying to build my app with webpack. The build was successful and it works as I expected. But, is there any problem with winston? If there is nothing to worry about, how to surpress the warning?
WARNING in ./~/winston/~/colors/lib/colors.js
Critical dependencies:
127:29-43 the request of a dependency is an expression
@ ./~/winston/~/colors/lib/colors.js 127:29-43
WARNING in ./~/winston/~/colors/lib/extendStringPrototype.js
Critical dependencies:
106:31-45 the request of a dependency is an expression
@ ./~/winston/~/colors/lib/extendStringPrototype.js 106:31-45
Issue Analytics
- State:
- Created 7 years ago
- Reactions:16
- Comments:18 (7 by maintainers)
Top Results From Across the Web
Webpack - Critical dependency: the request of a dependency ...
Webpack tries to resolve require calls statically to make a minimal bundle. When a library uses variables or expressions in a require call...
Read more >the request of a dependency is an expression webpack - You ...
When a library uses variables or expressions in a require call (such as require ('' + 'nodent') in these lines of ajv ),...
Read more >unclear how to resolve critical dependencies warning ... - GitHub
hi, when I run webpack, I get a warning message like: WARNING in node_modules/express/lib/view.js. Critical dependencies:
Read more >Integration with WebPack - Linkurious documentation
Critical dependency: the request of a dependency is an expression. This warning is due to a line in Ogma that attempts to require...
Read more >Dependency Management - webpack
A context is created if your request contains expressions, so the exact module is not known on compile time. Example, given we have...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have same issue after upgrade to webpack 2
The above issue still appears in v3.0.1. Any suggestions would be greatly appreciated.
Warnings:
Version info:
Also, apologies if I have done some dumb mistake.