node-sass

How to pre-load SASS custom utilities (variables and mixins) with webpack

♀尐吖头ヾ 提交于 2019-12-11 00:22:29
问题 I am loading my utilities and assets in base.scss like so @import "_variables"; @import "_mixins"; ... I have tons of modules in my application and we are doing so many changes in these modules. so importing the base.scss in the header of each of the scss files is causing so much trouble and seems very redundant. I tried using sass's includePaths but it didn't help as it only resolves the @import declarations. Is there any way that I can auto import my utilities without having to @import it

Unable to Publish Angular Application After Microsoft Build Engine Upgrade

痞子三分冷 提交于 2019-12-10 18:29:02
问题 Some time last week Microsoft DevOps upgraded the Build Engine from: Microsoft (R) Build Engine version 16.2.32702+c4012a063 for .NET Core TO Microsoft (R) Build Engine version 16.3.0+0f4c62fea for .NET Core It seems that this has update NODE to version 13 and has caused an Npm package (node-saas) installation to stop working... > node-sass@4.9.3 install D:\a\1\s\Website\ClientApp\node_modules\@angular-devkit\build-angular\node_modules\node-sass > node scripts/install.js Downloading binary

Why doesn't Sass `map-get()` return an error for a non-existent key?

房东的猫 提交于 2019-12-10 17:51:08
问题 Why doesn't map-get() throw an error when the key does not exist in the supplied map? For example: $map: ( 'keyone': 'value', 'keytwo': 'value', 'keythree': 'value' ); map-get($map, 'keyfour'); I'm aware of map-has-key() and I understand that might be useful on its own, but if I want to use map-get() smoothly, I shouldn't have to call map-has-key() each and every time. I'd expect the map-get() to throw an error, but instead it fails silently. Why is this not built into Sass? If it matters, I

node-sass-middleware only serving css file once

匆匆过客 提交于 2019-12-10 15:56:25
问题 I've made a really simple Express website that uses Jade and Sass, but I've run into a problem with my node-sass middleware. My server only serves a CSS file once, and then returns a 404 for every subsequent request. I have to restart the server to temporarily fix it. Here's my code; the server seems to be hang after outputting the css file (maybe, i'm not sure..) app.js: var express = require('express'), sassMiddleware = require('node-sass-middleware'); var app = express(); app.set('views',

Sass loader hangs compilation

≯℡__Kan透↙ 提交于 2019-12-10 15:38:44
问题 I am using webpack version 2.2.0 and sass-loader 4.4.1, and @angular/core is 2.4.4 when I run the command : npm run serve it make hang command prompt on 62% sometimes 61% or 63%. Here below id dev dependencies of package.json: "devDependencies": { "@types/core-js": "0.9.35", "@types/googlemaps": "3.26.2", "@types/node": "6.0.60", "@types/uglify-js": "2.0.27", "angular2-template-loader": "0.4.0", "awesome-typescript-loader": "2.2.4", "copy-webpack-plugin": "3.0.1", "css-loader": "0.25.0",

Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 6.x

扶醉桌前 提交于 2019-12-10 13:46:58
问题 I get following error message when running gulp : Error: Missing binding Z:\Themewagon\Premium\sparrow\zcore\node_modules\node-sass\vendor\win32-x64-48\binding.node Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 6.x Found bindings for the following Environments: Linux 64-bit with Node.js 7.x To resolve this error I tried: npm install node-sass, npm rebuild node-sass, npm uninstall -save node-sass, npm install -save node-sass, npm cache clean. etc

How to compile scss to css with node-sass

感情迁移 提交于 2019-12-10 04:01:48
问题 I have a master.scss with many imports from other .scss files. If I change a * .scss file master.css is generated automatically. I use only the NPM, no Gulp or Grunt! This should remain so. My current build script: "scripts": { "watch-sass": "sass --watch src/scss/master.scss:dist/css/master.css" } That's nice but takes a long time to compile! Now I'm trying to use node-sass. It should compile very fast. Unfortunately, I do not understand it completely ... node-sass is installed, via npm

Error running gulp-sass after update to Node v4.0.0

与世无争的帅哥 提交于 2019-12-09 17:32:59
问题 I updated to Node v4.0.0 and after when I run gulp in my projects I get an error with regards to gulp-sass/node-sass, as follows: Error: libsass bindings not found. Try reinstalling node-sass ? I've tried trashing all the node modules in the project and reinstalling, and I get some errors: npm WARN package.json package@0.0.0 No repository field. npm WARN package.json package@0.0.0 No license field. npm WARN deprecated CSSselect@0.4.1: the module is now available as 'css-select' npm WARN

Issue to node-sass and Docker

你说的曾经没有我的故事 提交于 2019-12-07 05:52:39
问题 I'm attempting to dockerise my node application. My current application is a nodejs express server with postgresql. ExpressJS uses node-sass-middleware to handle the sass assets. When I run node and postgresql locally on my OSX machine everything works fine. When I try to run the app with docker-compose I get a "Missing Binding error" Here is my Dockerfile: FROM node:7.2.1 RUN apt-get update -qq && apt-get install -y build-essential RUN apt-get install -y libpq-dev postgresql-client ENV APP

EACCES: permission denied, mkdir '/node_modules/node-sass/build' while running npm install on ubuntu

蹲街弑〆低调 提交于 2019-12-07 05:25:10
问题 i have an angular 4 app and i want to run it on ubuntu. i copied all project files , package.json and package-lock.json to a folder in winscp but i didn't copy node_modules! now when i run npm install, i get the errors like this: > node-sass@4.7.2 install /home/ubuntu/cms/node_modules/@angular/cli/node_modules/node-sass > node scripts/install.js Unable to save binary /home/ubuntu/cms/node_modules/@angular/cli/node_modules/node-sass/vendor/linux-x64-57 : { Error: EACCES: permission denied,