api, login, auth

1 files changed, 83 insertions, 0 deletions

diff --git a/node_modules/sass-loader/lib/loader.js b/node_modules/sass-loader/lib/loader.js
new file mode 100644
index 0000000..0a1fcd7
--- /dev/null
+++ b/node_modules/sass-loader/lib/loader.js
@@ -0,0 +1,83 @@
+"use strict";
+
+const sass = require("node-sass");
+const path = require("path");
+const async = require("neo-async");
+const formatSassError = require("./formatSassError");
+const webpackImporter = require("./webpackImporter");
+const normalizeOptions = require("./normalizeOptions");
+const pify = require("pify");
+
+// This queue makes sure node-sass leaves one thread available for executing
+// fs tasks when running the custom importer code.
+// This can be removed as soon as node-sass implements a fix for this.
+const threadPoolSize = process.env.UV_THREADPOOL_SIZE || 4;
+const asyncSassJobQueue = async.queue(sass.render, threadPoolSize - 1);
+
+/**
+ * The sass-loader makes node-sass available to webpack modules.
+ *
+ * @this {LoaderContext}
+ * @param {string} content
+ */
+function sassLoader(content) {
+    const callback = this.async();
+    const isSync = typeof callback !== "function";
+    const self = this;
+    const resourcePath = this.resourcePath;
+
+    function addNormalizedDependency(file) {
+        // node-sass returns POSIX paths
+        self.dependency(path.normalize(file));
+    }
+
+    if (isSync) {
+        throw new Error("Synchronous compilation is not supported anymore. See https://github.com/webpack-contrib/sass-loader/issues/333");
+    }
+
+    const options = normalizeOptions(this, content, webpackImporter(
+        resourcePath,
+        pify(this.resolve.bind(this)),
+        addNormalizedDependency
+    ));
+
+    // Skip empty files, otherwise it will stop webpack, see issue #21
+    if (options.data.trim() === "") {
+        callback(null, "");
+        return;
+    }
+
+    // start the actual rendering
+    asyncSassJobQueue.push(options, (err, result) => {
+        if (err) {
+            formatSassError(err, this.resourcePath);
+            err.file && this.dependency(err.file);
+            callback(err);
+            return;
+        }
+
+        if (result.map && result.map !== "{}") {
+            result.map = JSON.parse(result.map);
+            // result.map.file is an optional property that provides the output filename.
+            // Since we don't know the final filename in the webpack build chain yet, it makes no sense to have it.
+            delete result.map.file;
+            // The first source is 'stdin' according to node-sass because we've used the data input.
+            // Now let's override that value with the correct relative path.
+            // Since we specified options.sourceMap = path.join(process.cwd(), "/sass.map"); in normalizeOptions,
+            // we know that this path is relative to process.cwd(). This is how node-sass works.
+            result.map.sources[0] = path.relative(process.cwd(), resourcePath);
+            // node-sass returns POSIX paths, that's why we need to transform them back to native paths.
+            // This fixes an error on windows where the source-map module cannot resolve the source maps.
+            // @see https://github.com/webpack-contrib/sass-loader/issues/366#issuecomment-279460722
+            result.map.sourceRoot = path.normalize(result.map.sourceRoot);
+            result.map.sources = result.map.sources.map(path.normalize);
+        } else {
+            result.map = null;
+        }
+
+        result.stats.includedFiles.forEach(addNormalizedDependency);
+        callback(null, result.css.toString(), result.map);
+    });
+}
+
+module.exports = sassLoader;