evilebottnawi

sokra

jhnns

sass-loader

Object.defineProperty(exports, "__esModule", {

exports.getModernWebpackImporter = getModernWebpackImporter;

exports.getSassImplementation = getSassImplementation;

exports.getWebpackImporter = getWebpackImporter;

exports.getWebpackResolver = getWebpackResolver;

exports.normalizeSourceMap = normalizeSourceMap;

var _url = _interopRequireDefault(require("url"));

var _path = _interopRequireDefault(require("path"));

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

function getDefaultSassImplementation() {

        require.resolve("sass-embedded");

  // eslint-disable-next-line import/no-dynamic-require, global-require

 * This function is not Webpack-specific and can be used by tools wishing to mimic `sass-loader`'s behaviour, so its signature should not be changed.

function getSassImplementation(loaderContext, implementation) {

  let resolvedImplementation = implementation;

    resolvedImplementation = getDefaultSassImplementation();

  if (typeof resolvedImplementation === "string") {

    // eslint-disable-next-line import/no-dynamic-require, global-require

    resolvedImplementation = require(resolvedImplementation);

    throw new Error("Unknown Sass implementation.");

    throw new Error(`Unknown Sass implementation "${info}".`);

  const [implementationName] = infoParts;

  if (implementationName === "dart-sass") {

    // eslint-disable-next-line consistent-return

  } else if (implementationName === "node-sass") {

  } else if (implementationName === "sass-embedded") {

  throw new Error(`Unknown Sass implementation "${implementationName}".`);

function isProductionLikeMode(loaderContext) {

  return loaderContext.mode === "production" || !loaderContext.mode;

function proxyCustomImporters(importers, loaderContext) {

  return [].concat(importers).map(importer => function proxyImporter(...args) {

      webpackLoaderContext: loaderContext

 * Derives the sass options from the loader context and normalizes its values with sane defaults.

const IS_MODULE_IMPORT = /^~([^/]+|[^/]+\/|@[^/]+[/][^/]+|@[^/]+\/?|@[^/]+[/][^/]+\/)$/;

 * When `sass`/`node-sass` tries to resolve an import, it uses a special algorithm.

 * Since the `sass-loader` uses webpack to resolve the modules, we need to simulate that algorithm.

 * This function returns an array of import paths to try.

 * The last entry in the array is always the original url to enable straight-forward webpack.config aliases.

 * We don't need emulate `dart-sass` "It's not clear which file to import." errors (when "file.ext" and "_file.ext" files are present simultaneously in the same directory).

 * This reduces performance and `dart-sass` always do it on own side.

url, forWebpackResolver = false, fromImport = false) {

  // In case there is module request, send this to webpack resolver

    if (MODULE_REQUEST_REGEX.test(url)) {

      request = request.replace(MODULE_REQUEST_REGEX, "");

      return [...new Set([request, url])];

    if (IS_MODULE_IMPORT.test(url) || IS_PKG_SCHEME.test(url)) {

      request = request[request.length - 1] === "/" ? request : `${request}/`;

  // Keep in mind: ext can also be something like '.datepicker' when the true extension is omitted and the filename contains a dot.

  // @see https://github.com/webpack-contrib/sass-loader/issues/167

  const extension = _path.default.extname(request).toLowerCase();

  // Because @import is also defined in CSS, Sass needs a way of compiling plain CSS @imports without trying to import the files at compile time.

  // To accomplish this, and to ensure SCSS is as much of a superset of CSS as possible, Sass will compile any @imports with the following characteristics to plain CSS imports:

  //  - imports where the URL ends with .css.

  //  - imports where the URL begins http:// or https://.

  //  - imports where the URL is written as a url().

  // The `node-sass` package sends `@import` ending on `.css` to importer, it is bug, so we skip resolve

  const dirname = _path.default.dirname(request);

  const normalizedDirname = dirname === "." ? "" : `${dirname}/`;

  const basename = _path.default.basename(request);

  const basenameWithoutExtension = _path.default.basename(request, extension);

  return [...new Set([].concat(fromImport ? [`${normalizedDirname}_${basenameWithoutExtension}.import${extension}`, `${normalizedDirname}${basenameWithoutExtension}.import${extension}`] : []).concat([`${normalizedDirname}_${basename}`, `${normalizedDirname}${basename}`]).concat(forWebpackResolver ? [url] : []))];

function promiseResolve(callbackResolve) {

  return (context, request) => new Promise((resolve, reject) => {

    callbackResolve(context, request, (error, result) => {

async function startResolving(resolutionMap) {

    return await resolve(context, possibleRequests[0]);

    const [, ...tailResult] = possibleRequests;

      const [, ...tailResolutionMap] = resolutionMap;

      return startResolving(tailResolutionMap);

    // eslint-disable-next-line no-param-reassign

    resolutionMap[0].possibleRequests = tailResult;

    return startResolving(resolutionMap);

const IS_SPECIAL_MODULE_IMPORT = /^~[^/]+$/;

// `[drive_letter]:\` + `\\[server]\[sharename]\`

const IS_NATIVE_WIN32_PATH = /^[a-z]:[/\\]|^\\\\/i;

 * Create the resolve function used in the custom Sass importer.

 * Can be used by external tools to mimic how `sass-loader` works, for example

 * in a Jest transform. Such usages will want to wrap `resolve.create` from

 * [`enhanced-resolve`]{@link https://github.com/webpack/enhanced-resolve} to

 * pass as the `resolverFactory` argument.

 * @param {Function} resolverFactory - A factory function for creating a Webpack

 * @param {Object} implementation - The imported Sass implementation, both

 *   `sass` (Dart Sass) and `node-sass` are supported.

 * @param {string[]} [includePaths] - The list of include paths passed to Sass.

 * @throws If a compatible Sass implementation cannot be found.

function getWebpackResolver(resolverFactory, implementation, includePaths = []) {

  const isDartSass = implementation && implementation.info.includes("dart-sass");

  // We only have one difference with the built-in sass resolution logic and out resolution logic:

  // First, we look at the files starting with `_`, then without `_` (i.e. `_name.sass`, `_name.scss`, `_name.css`, `name.sass`, `name.scss`, `name.css`),

  // although `sass` look together by extensions (i.e. `_name.sass`/`name.sass`/`_name.scss`/`name.scss`/`_name.css`/`name.css`).

  // It shouldn't be a problem because `sass` throw errors:

  // - on having `_name.sass` and `name.sass` (extension can be `sass`, `scss` or `css`) in the same directory

  // - on having `_name.sass` and `_name.scss` in the same directory

  // Also `sass` prefer `sass`/`scss` over `css`.

  const sassModuleResolve = promiseResolve(resolverFactory({

    !IS_SPECIAL_MODULE_IMPORT.test(request) &&

    // We need improve absolute paths handling.

    // Absolute paths should be resolved:

    // - Server-relative URLs - `<context>/path/to/file.ext` (where `<context>` is root context)

    // - Absolute path - `/full/path/to/file.ext` or `C:\\full\path\to\file.ext`

    !isFileScheme && !originalRequest.startsWith("/") && !IS_NATIVE_WIN32_PATH.test(originalRequest);

    if (includePaths.length > 0 && needEmulateSassResolver) {

      // The order of import precedence is as follows:

      // 1. Filesystem imports relative to the base file.

      // 3. Filesystem imports relative to the working directory.

      // 4. Filesystem imports relative to an `includePaths` path.

      // 5. Filesystem imports relative to a `SASS_PATH` path.

      // `sass` run custom importers before `3`, `4` and `5` points, we need to emulate this behavior to avoid wrong resolution.

      const sassPossibleRequests = getPossibleRequests(request, false, fromImport);

      // `node-sass` calls our importer before `1. Filesystem imports relative to the base file.`, so we need emulate this too

        resolutionMap = resolutionMap.concat({

          resolve: fromImport ? sassImportResolve : sassModuleResolve,

          context: _path.default.dirname(context),

          possibleRequests: sassPossibleRequests

      resolutionMap = resolutionMap.concat(

      // eslint-disable-next-line no-shadow

    const webpackPossibleRequests = getPossibleRequests(request, true, fromImport);

    resolutionMap = resolutionMap.concat({

      resolve: fromImport ? webpackImportResolve : webpackModuleResolve,

      context: _path.default.dirname(context),

      possibleRequests: webpackPossibleRequests

function getWebpackImporter(loaderContext, implementation, includePaths) {

  const resolve = getWebpackResolver(loaderContext.getResolve, implementation, includePaths);

  return function importer(originalUrl, prev, done) {

    resolve(prev, originalUrl, fromImport).then(result => {

      // Although we're also using stats.includedFiles, this might come in handy when an error occurs.

      // In this case, we don't get stats.includedFiles from node-sass/sass.

      loaderContext.addDependency(_path.default.normalize(result));

      // By removing the CSS file extension, we trigger node-sass to include the CSS file instead of just linking it.

        file: result.replace(MATCH_CSS, "")

    // Catch all resolving errors, return the original file and pass responsibility back to other custom importers

 * Verifies that the implementation and version of Sass is supported by this loader.

function getCompileFn(implementation, options) {

  const isNewSass = implementation.info.includes("dart-sass") || implementation.info.includes("sass-embedded");

        return implementation.compileStringAsync(data, rest);

  "description": "Sass loader for webpack",

  "repository": "webpack-contrib/sass-loader",

  "homepage": "https://github.com/webpack-contrib/sass-loader",

  "bugs": "https://github.com/webpack-contrib/sass-loader/issues",

    "url": "https://opencollective.com/webpack"

    "build": "cross-env NODE_ENV=production babel src -d dist --copy-files",

    "commitlint": "commitlint --from=master",

    "security": "npm audit --production",

    "lint:prettier": "prettier --cache --list-different .",

    "lint:spelling": "cspell --cache --no-must-find-files --quiet \"**/*.*\"",

    "lint": "npm-run-all -l -p \"lint:**\"",

    "test:only": "cross-env NODE_ENV=test jest",

    "fix:js": "npm run lint:js -- --fix",

    "fix:prettier": "npm run lint:prettier -- --write",

    "fix": "npm-run-all -l fix:js fix:prettier",

    "test:watch": "npm run test:only -- --watch",

    "test:manual": "npm run build && webpack-dev-server test/manual/src/index.js --open --config test/manual/webpack.config.js",

    "test:coverage": "npm run test:only -- --collectCoverageFrom=\"src/**/*.js\" --coverage",

    "prepare": "husky install && npm run build",

    "node-sass": "^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^9.0.0",

    "@commitlint/config-conventional": "^18.4.4",

    "@webpack-contrib/eslint-config-webpack": "^3.0.0",

    "bootstrap-v4": "npm:bootstrap@^4.5.3",

    "bootstrap-v5": "npm:bootstrap@^5.0.1",

    "jest-environment-node-single-context": "^29.1.0",

		@@ -231,2 +231,3 @@ "use strict";
		const IS_MODULE_IMPORT = /^~([^/]+\|[^/]+\/\|@[^/]+[/][^/]+\|@[^/]+\/?\|@[^/]+[/][^/]+\/)$/;
		const IS_PKG_SCHEME = /^pkg:/i;

		@@ -257,3 +258,7 @@ /**
		}
		if (IS_MODULE_IMPORT.test(url)) {
		if (IS_PKG_SCHEME.test(url)) {
		request = `${request.slice(4)}`;
		return [...new Set([request, url])];
		}
		if (IS_MODULE_IMPORT.test(url) \|\| IS_PKG_SCHEME.test(url)) {
		request = request[request.length - 1] === "/" ? request : `${request}/`;
		@@ -421,2 +426,4 @@ return [...new Set([request, url])];
		!IS_SPECIAL_MODULE_IMPORT.test(request) &&
		// don't handle `pkg:` scheme
		!IS_PKG_SCHEME.test(request) &&
		// We need improve absolute paths handling.
		@@ -423,0 +430,0 @@ // Absolute paths should be resolved:

		{
		"name": "sass-loader",
		"version": "14.1.0",
		"version": "14.1.1",
		"description": "Sass loader for webpack",
		@@ -38,3 +38,3 @@ "license": "MIT",
		"test": "npm run test:coverage",
		"prepare": "husky install && npm run build",
		"prepare": "husky && npm run build",
		"release": "standard-version"
		@@ -94,3 +94,3 @@ },
		"foundation-sites": "^6.7.5",
		"husky": "^8.0.3",
		"husky": "^9.0.11",
		"jest": "^29.6.2",
		@@ -97,0 +97,0 @@ "jest-environment-node-single-context": "^29.1.0",

Improved metrics