The issue I am encountering involves the aurelia skeleton-typescript-webpack project. When attempting to debug the TypeScript code in Chrome, the breakpoints do not align properly with where the program actually stops. Here's an example:
After placing a debugger statement on line 18, Chrome stopped execution at line 23. It seems like it should have stopped at the correct location since "i" has a value but "a" does not.
Do you have any suggestions for resolving this problem?
I am utilizing the skeleton-typescript-webpack project without making any modifications other than to lines 17, 18, and 19. The application is being run using the "npm run webpack-dev-server" command with Node version v6.9.1 and npm version 4.0.2