-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
.js.map file contains absolute file path instead of site relative path #496
Comments
@wforney, What does your repro code for this issue looks like? What are the compiler options you are using to compiler TypeScript. I would need some sample code to look into this. thanks. |
Install VS 2013 Update 3. The code I'm compiling is irrelevant. |
I did these steps: Js file as well as map did not contain c:.... etc. file1.ts: class c {
} file.js var c = (function () {
function c() {
}
return c;
})();
//# sourceMappingURL=file1.js.map file1.js.map
I am going to try with WebEssentials after this. |
Installed latest WebEssentials and followed the steps and still don't see the issue you are reporting. These are the same results as without webessentials class c {
} file.js var c = (function () {
function c() {
}
return c;
})();
//# sourceMappingURL=file1.js.map file1.js.map
|
this one? |
I have the map root set to $(ProjectDir) in VS. Could that be causing this? |
Yes setting of the mapRoot would change how the sourcemaps are emitted. It is used to specify where the maps common directory where the maps would be present when the program would be debugged. You should do this only if have special build step that moves sources, maps or js files around or your app/page needs some special steps of authorization. |
See similar issue here that was in Web Essentials for LESS: madskristensen/WebEssentials2013#1424 (comment)
Should not see C:\some\path\here\whatever.js in the map file. Should be like /here/whatever.js relative path instead. Otherwise source control will be a headache (always modified between different devs).
The text was updated successfully, but these errors were encountered: