Closed nawlbergs closed 1 year ago
I was able to remote into my windows 10 machine and verify that the problem also on windows....
Update: this seems to be related to arrow functions that have generics... removing all arrow functions that have a generic ( or converting them to a standard function ) seems to resolve it... at least in this scenario...
I'm finding it hard to believe no one else is running into this.
Most likely not related to NX ... but anyone have thoughts on what repo this should get posted to? ts-loader? webpack?
@AgentEnder you can close this: https://bugs.chromium.org/p/chromium/issues/detail?id=1403355
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
Not sure if this is a chrome issue, an issue with webpack, nx or what... but Im posting it here... because I started to rewrite our production application with nrwl and quickly hit a major blocker with the node/express application.
The chrome debugger just completely falls apart in certain files. The tooltips stop working, color coding disappears and variables/methods are missing from scope. (this did not occur at all in our legacy and much much large express app)
I took a weed-whacker to the nx app - removed everything possible and pushed up a public repo.
Expected Behavior
Dev tools work
Github Repo
https://github.com/nawlbergs/dev-tools-issue
Steps to Reproduce
git clone https://github.com/nawlbergs/dev-tools-issue
npm i
npm start
Nx Report
Failure Logs
No response
Additional Information
No response