SCSS file served via webpack dev server is different than source
So basically I use webpack, to compile sass files.
Here is the dev config:
https://pastebin.com/HqqU1szG
My problem is, that when i have SCSS written like so:
.something
color: red;
What gets served in my browser web tools looks like so:
.something
color:red;
As a consequence, when I inspect .something, in my browser (or rather something that matches rule further down in css file, the line number reported in dev tools does not match.
What could I do to fix this?
webpack sass
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
add a comment |
So basically I use webpack, to compile sass files.
Here is the dev config:
https://pastebin.com/HqqU1szG
My problem is, that when i have SCSS written like so:
.something
color: red;
What gets served in my browser web tools looks like so:
.something
color:red;
As a consequence, when I inspect .something, in my browser (or rather something that matches rule further down in css file, the line number reported in dev tools does not match.
What could I do to fix this?
webpack sass
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
Use source maps. If all lines are staying where they were, you don't need webpack in the first place, so the fact that lines aren't corresponding is perfectly normal. Now, if lines are not staying where they were, source maps will tell developer tools where to find the original lines. Use source maps.
– Amadan
Nov 15 '18 at 9:12
I am using source maps. But for some reason, as I stated chrome or webpack (i am not sure) reformats my SCSS in different style, therefore throwing off the line numbers
– galdikas
Nov 15 '18 at 9:17
Not sure, I thinkfast-sass-loaderdoesn't support source maps.
– Amadan
Nov 15 '18 at 9:18
add a comment |
So basically I use webpack, to compile sass files.
Here is the dev config:
https://pastebin.com/HqqU1szG
My problem is, that when i have SCSS written like so:
.something
color: red;
What gets served in my browser web tools looks like so:
.something
color:red;
As a consequence, when I inspect .something, in my browser (or rather something that matches rule further down in css file, the line number reported in dev tools does not match.
What could I do to fix this?
webpack sass
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
So basically I use webpack, to compile sass files.
Here is the dev config:
https://pastebin.com/HqqU1szG
My problem is, that when i have SCSS written like so:
.something
color: red;
What gets served in my browser web tools looks like so:
.something
color:red;
As a consequence, when I inspect .something, in my browser (or rather something that matches rule further down in css file, the line number reported in dev tools does not match.
What could I do to fix this?
webpack sass
webpack sass
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
asked Nov 15 '18 at 9:07
galdikasgaldikas
70721131
70721131
Use source maps. If all lines are staying where they were, you don't need webpack in the first place, so the fact that lines aren't corresponding is perfectly normal. Now, if lines are not staying where they were, source maps will tell developer tools where to find the original lines. Use source maps.
– Amadan
Nov 15 '18 at 9:12
I am using source maps. But for some reason, as I stated chrome or webpack (i am not sure) reformats my SCSS in different style, therefore throwing off the line numbers
– galdikas
Nov 15 '18 at 9:17
Not sure, I thinkfast-sass-loaderdoesn't support source maps.
– Amadan
Nov 15 '18 at 9:18
add a comment |
Use source maps. If all lines are staying where they were, you don't need webpack in the first place, so the fact that lines aren't corresponding is perfectly normal. Now, if lines are not staying where they were, source maps will tell developer tools where to find the original lines. Use source maps.
– Amadan
Nov 15 '18 at 9:12
I am using source maps. But for some reason, as I stated chrome or webpack (i am not sure) reformats my SCSS in different style, therefore throwing off the line numbers
– galdikas
Nov 15 '18 at 9:17
Not sure, I thinkfast-sass-loaderdoesn't support source maps.
– Amadan
Nov 15 '18 at 9:18
Use source maps. If all lines are staying where they were, you don't need webpack in the first place, so the fact that lines aren't corresponding is perfectly normal. Now, if lines are not staying where they were, source maps will tell developer tools where to find the original lines. Use source maps.
– Amadan
Nov 15 '18 at 9:12
Use source maps. If all lines are staying where they were, you don't need webpack in the first place, so the fact that lines aren't corresponding is perfectly normal. Now, if lines are not staying where they were, source maps will tell developer tools where to find the original lines. Use source maps.
– Amadan
Nov 15 '18 at 9:12
I am using source maps. But for some reason, as I stated chrome or webpack (i am not sure) reformats my SCSS in different style, therefore throwing off the line numbers
– galdikas
Nov 15 '18 at 9:17
I am using source maps. But for some reason, as I stated chrome or webpack (i am not sure) reformats my SCSS in different style, therefore throwing off the line numbers
– galdikas
Nov 15 '18 at 9:17
Not sure, I think
fast-sass-loader doesn't support source maps.– Amadan
Nov 15 '18 at 9:18
Not sure, I think
fast-sass-loader doesn't support source maps.– Amadan
Nov 15 '18 at 9:18
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53315812%2fscss-file-served-via-webpack-dev-server-is-different-than-source%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53315812%2fscss-file-served-via-webpack-dev-server-is-different-than-source%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Use source maps. If all lines are staying where they were, you don't need webpack in the first place, so the fact that lines aren't corresponding is perfectly normal. Now, if lines are not staying where they were, source maps will tell developer tools where to find the original lines. Use source maps.
– Amadan
Nov 15 '18 at 9:12
I am using source maps. But for some reason, as I stated chrome or webpack (i am not sure) reformats my SCSS in different style, therefore throwing off the line numbers
– galdikas
Nov 15 '18 at 9:17
Not sure, I think
fast-sass-loaderdoesn't support source maps.– Amadan
Nov 15 '18 at 9:18