Skip to content
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

Debugging #85

Closed
ccolonna opened this issue Sep 2, 2020 · 2 comments
Closed

Debugging #85

ccolonna opened this issue Sep 2, 2020 · 2 comments
Labels

Comments

@ccolonna
Copy link

ccolonna commented Sep 2, 2020

Is there a way to attach a debugger to ld-r process (VScode debugger, ChromeDevTools, ...) ?
I'm finding difficulties on managing to work a debugger with this isomorphic app bundled with webpack.
I'm not sure (just guessing) but I wonder if the transformation operated by webpack + babel cuts
the map with original files.
Do someone already face this problem?

Expected Behavior

Code execution stops on breakpoint both on client and server files.

Actual Behavior

Breakpoint not working

Steps to Reproduce the Problem

  1. Launch $ node --inspect webpack/dev-server.js from ld-r root directory
  2. attach a debugger to the running process
  3. Navigate to a file and set a breakpoint (in Chrome Dev Tools)

Specifications

  • Version:
  • Platform:
  • Subsystem:
@ali1k ali1k added the question label Sep 8, 2020
@ali1k
Copy link
Owner

ali1k commented Sep 8, 2020

I am not aware of any. Maybe you can find some tools for https://fluxible.io that is basically the framework behind ld-r.

@ccolonna
Copy link
Author

Cannot be able to find any debugger working with fluxible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants