Closed Bitfiddler closed 7 years ago
@Bitfiddler Pushed a new release out (0.6.2). Should fix this issue. Let us know if that works.
I was unable to test 0.6.2, but I attempted to migrate to 0.6.4 and it causes SystemJs loading errors so I have reverted back to 0.4.0 again.
I'm submitting a bug report
Please tell us about your environment:
Operating System: Windows 7
Node Version: 6.2.0
NPM Version: 4.1.1
JSPM OR Webpack AND Version JSPM 0.16.53
Browser: Chrome Version 58.0.3029.110 (64-bit)
Language: TypeScript 2.4.0
Current behavior: I have my bundles.js config set to be inline, the bundler produces a separate (invalid) map file anyway with contents 'undefined' inside. It then appends a second sourcemap URL entry inside the app bundle after the base64 encoded inline content.
What is the expected behavior? Expected behavior is what happens in 0.4.0, the inline encoded sourcemap url is the only entry in the app-build.js file and there is no invalid app-build.js.map file generated. I have reverted to 0.4.0 to get work done.
What is the motivation / use case for changing the behavior? So that I can debug successfully in Chrome.