Easy way to debug context graph #19611
Unanswered
ConcernedHobbit
asked this question in
Q&A
Replies: 1 comment
-
|
I want to say better way is profiling - https://developer.chrome.com/docs/devtools/performance/nodejs#:~:text=DevTools%20lets%20you%20profile%20JavaScript,will%20show%20you%20the%20results., also you can try |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I have a currently untraceable problem with a 3rd-party dependency (
react-styleguidist) and webpack where an entire monorepo (incl.node_modules) is scanned into context, slowing down build times massively and causing issues in CI.Is there some easy way to diagnose what loader is causing this behaviour? I'm currently running into a wall with the AsyncQueue abstractions, as they hide the tree both in error stack traces as well as when inspecting with dev tools.
Beta Was this translation helpful? Give feedback.
All reactions