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.
Sourcemaps not set up correctly?
See original GitHub issueI’m trying to debug #10 , but I don’t see any indication of the proxy-memoize source showing up in the Chrome DevTools. I can’t find any filenames with proxy-memoize in the path, and if I try to put a breakpoint right before the memoize() call and step into it, the DevTools debugger steps into random lines of the RTK source before ending up back in the app code.
This is using https://github.com/reduxjs/redux-fundamentals-example-app/commit/f270ea1c91362c74e1ca88a4982d8545b4984b11 , which is built with react-scripts@3.4.3.
Just wondering if somehow the sourcemaps aren’t built/defined correctly.
On the other hand, loading https://codesandbox.io/s/proxy-memoize-demo-c1021 into Chrome, I see the proxy-memoize files under node_modules just fine. So, this could also be a build environment issue somehow.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
If this issue isn’t super critical, I will consider to make this library v1.0.0.
Closing as nothing actionable. Can reopen if someone has a suggestion.