-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Critial Dependency: the request of a dependency is an expression when upgrading to 4.0.0-beta.3 from beta.2 #3361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
No related to webpack-dev-server and please do not ignore questions in the issue template |
You rewrite |
After some more digging. I've found the cause to be related to the experimental plugin Upgrading it to 0.5.0-beta.8 loads the site correctly, but produces this overlay error. If that means we can close the issue at this time, then that makes sense to me! |
If you provide example of repo I can look at code, maybe we need fix the problem in |
The problem with that is that our repo at work is private. I'm trying to isolate things in a such a way that I can find the issue. Updating If I disable the overlay, everything is fine so I think I was mistaken in thinking that plugin caused any issues |
It means you have the same file, I think problem in |
I think this is all we have? it's not a very complex webpack setup resolve: {
extensions,
plugins: [new TsconfigPathsPlugin({ extensions: ['.tsx', '.ts', '.js'] })],
}, The production cli output is definitely more helpful.
I tried upgrading We've been on Would you consider this a piece of tech debt that we need to resolve before upgrading webpack-dev-sever? |
Yep, circular dependencies, we can't fix it here |
So I guess the thing is, it's a warning on the CLI and doesn't cause any issues. But when using the webpack dev server, it shows as an error that I cannot "X" out of. Turning the overlay off would be the workaround. |
Please create minimum reproducible test repo, I will look |
Sure. I’ll post back when I create it |
Hey there @alexander-akait, have you gotten a chance to look at the repo? |
Tomorrow (5.06) |
I have the same problem on 4.0.0-beta.3 |
Update
in |
@alexander-akait I don't think this is a solution because
|
I don't have this problem, please check my steps again, anyway this problem with |
I understand that but the |
Got it, let's allow to close overlay, now you can use:
also we have |
Thanks! Adding that package to |
Code
Please paste the results of
webpack-cli info
here, and mention other relevant informationExpected Behavior
Loads the website
Actual Behavior
For Bugs; How can we reproduce the behavior?
Not entirely sure other than to use webpack-dev-server 4.0.0-beta.3, with the above webpack configuration.
I'm not able to find out exactly what is causing this issue given the limited output.
For Features; What is the motivation and/or use-case for the feature?
The text was updated successfully, but these errors were encountered: