Closed zoao closed 6 years ago
I changed this in my webpack.config and now i can debug in chrome.
ENV === 'test' || ENV === 'development' ? envDev(ENV === 'test' ? {} : { devtool: 'inline-source-map' }) : envProd({ /* devtool: '...' */ }),
Thank you @cluka , because of this change, we can now debug in chrome again. I think it´s a bug in the skeleton template. Changing !== to === corrected our wrong sourcemaps.
can be closed
I'm submitting a bug report
Aurelia Skeleton Version skeleton-typescript-webpack
Framework Version: aurelia-skeleton-navigation-webpack@1.1.2
Please tell us about your environment:
Operating System: Windows 10
Node Version: 6.9.2
NPM Version: 4.0.5
JSPM OR Webpack AND Version webpack 2.1.0-beta.27
Browser: Chrome 55
Language: TypeScript 2.1.4
Current behavior: With default webpack.config.ts setting, I Could not debug
Expected/desired behavior: 1- In Visual Code I have installed the extension Debugger for Chrome 2.4.2 2- I create the file launch,json:
3- The execution not stop in breakpoints in Visual Code 4- I did a lot of testing and research and with the following changes in webpack.config.ts it works fine:
5- The debug in chrome also work good, but when I start debugging in Visual Code, if I try to open the "chrome developer tools", the chrome closes.
In my tests the debug in chrome developer tools is also not working, because this line: