Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Debugging a Chrome Extension in development mode #60

Open
duliba opened this issue Feb 19, 2019 · 2 comments
Open

Debugging a Chrome Extension in development mode #60

duliba opened this issue Feb 19, 2019 · 2 comments

Comments

@duliba
Copy link

duliba commented Feb 19, 2019

I followed the instructions to start the development server in debug mode:
NODE_ENV=development npm run start

However, when I look at the source code in Chrome DevTools, everything seems to be bundled and optimized, and I don't even find some bundles:
screen shot 2019-02-20 at 00 14 01

From the image you can tell that the code is optimized, and that some bundles (like popup.bundle.js and options.bundle.js) don't even show up.

Any idea if there's a way around this to allow dynamic debugging?

Thanks :)

@samuelsimoes
Copy link
Owner

This code isn't the optimized code, this is the code that webpack generates in order to allow the hot reload compilation.

I don't understand exactly what do you want to mean with "dynamic debugging" but if you, for example, put a console.log('hello') on your code and click in the file line in the right, you get the code before the transpilation.

image

@laiqun
Copy link

laiqun commented Jan 21, 2022

hi duliba:
You can try this way:
image
Then select file you want to debug:
image

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

No branches or pull requests

3 participants