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.
Ahh. I had to remember this: underscore prefix turns an imported sass-file into a partial, which should be done anyways for performance optimization. Thanks!
npm -v
): 6.4.1node -v
): 10.15node -p process.versions
): {http_parser: '2.8.0',
node: '10.15.0',
v8: '6.8.275.32-node.45',
uv: '1.23.2',
zlib: '1.2.11',
ares: '1.15.0',
modules: '64',
nghttp2: '1.34.0',
napi: '3',
openssl: '1.1.0j',
icu: '62.1',
unicode: '11.0',
cldr: '33.1',
tz: '2018e'
}
node -p process.platform
): darwinnode -p process.arch
): x64node -p "require('node-sass').info"
):node-sass 4.12.0 (Wrapper) [JavaScript]
libsass 3.5.4 (Sass Compiler) [C/C++]
npm ls node-sass
): node-sass@4.12.0main.scss contains:
mixins.scss contains:
home.scss contains something like
package.json contains scripts like:
running cssWatch results in an output like that (using yarn, but npm is doing the same):
However, the file is properly written, containing the mixin's condition!
If i run cssDev the main.css is written without any issues.
Any explanation for that behaviour?
The text was updated successfully, but these errors were encountered: