You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
I've noticed that when I DevTools inspect styles from imported *.scss files, it always pointing to the main custom.scss instead of _headers.scss or _typography.scss
The text was updated successfully, but these errors were encountered:
cachaito
changed the title
Souce maps doesn't work correctly (node-sass from CLI)
Source maps doesn't work correctly (node-sass from CLI)
Apr 4, 2015
This issue belongs to LibSass. node-sass does not alter source-maps generate by LibSass.
LibSass recently fixed some source-map related issues, you can retest your usecase using v3 beta.
Thank You for answer @am11. I've tested node-sass@3.0.0-beta.5 and amazingly simple: node-sass --watch --source-map true scss/custom.scss -o .tmp/css works correctly. Amazingly even the flag --watch works fine! (except every second *.scss save node-sass yields:
{
"message": "File to read not found or unreadable: D:\\somePath\\scss\\custom.scss",
"status": 4
}
Hi!
Tested environment:
Win7 64bit
,Node 0.12.2
,node-sass 2.1.1
Code from Npm scripts CLI:
I've noticed that when I DevTools inspect styles from imported *.scss files, it always pointing to the main custom.scss instead of _headers.scss or _typography.scss
The text was updated successfully, but these errors were encountered: