# node-sass-custom-importer

> A custom importer for node-sass to enable importing files from node packages

Latest version **1.1.0** (published 2015-07-15) · MIT license · 0 weekly downloads

## Install

```sh
npm install node-sass-custom-importer
pnpm add node-sass-custom-importer
yarn add node-sass-custom-importer
bun add node-sass-custom-importer
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.1.0 |
| Published | 2015-07-15 |
| First published | 2015-07-15 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 8 |
| Author | Daniel de la Cruz |
| Maintainers | danderu |
| Keywords | node, sass, importer |

## Links

- npm: https://www.npmjs.com/package/node-sass-custom-importer
- Repository: https://github.com/danderu/node-sass-custom-importer
- Homepage: https://github.com/danderu/node-sass-custom-importer#readme
- Issues: https://github.com/danderu/node-sass-custom-importer/issues
- npm.io page: https://npm.io/package/node-sass-custom-importer

## Alternatives

- [@expo/fingerprint](https://npm.io/package/@expo/fingerprint.md) — 6.2M weekly downloads
- [@azure/monitor-opentelemetry-exporter](https://npm.io/package/@azure/monitor-opentelemetry-exporter.md) — 850.0K weekly downloads
- [@azure/monitor-opentelemetry](https://npm.io/package/@azure/monitor-opentelemetry.md) — 624.0K weekly downloads
- [@posthog/ai](https://npm.io/package/@posthog/ai.md) — 423.3K weekly downloads
- [fakefilter](https://npm.io/package/fakefilter.md) — 63.9K weekly downloads

## Recent versions

- 1.1.0 (latest) — 2015-07-15

## README

# node-sass-custom-importer
## installation

```
npm install node-sass-custom-importer
```

## usage and description
Custom importer is an experimental feature of node-sass (https://github.com/sass/node-sass). You can read more about it here:
https://github.com/sass/node-sass#importer--v200---experimental

With this custom importer, you can import any .scss or .sass files available in the node packages of your application without a relative path. This custom importer resolves issues like the following ones:
* http://www.mindscapehq.com/forums/thread/232248
* http://stackoverflow.com/questions/6502313/sass-import-a-file-from-a-different-directory

If you have an app with the following folder structure:
```
├── node_modules
│   └── my-theme
│       ├── dist
│       │   ├── styles.scss
│   └── my-component
│       ├── node_modules
|··     ├── src
|··     |·· ├── styles.scss
|·· index.js
```
You have installed the package "my-theme" with your styles and "my-component" with your component, which has a dependency of "my-theme" as well. But, when you install both packages in a higher order component, both packages are installed at the root app's node_modules folder. This causes the relative imports in your SASS files to break.

To fix this inconvenience, with this importer, you can do:

```
@import '~my-theme/dist/styles'
```

And in your packages.json, add the following script:

```
"build:styles": "node-sass src/index.scss dist/index.css --importer ./node_modules/node-sass-custom-importer/importer.js",
```

So, when you run `npm run build:styles`, the importer will look recursively in its own `node_modules` folder first, and then in its parent `node_modules` folders.

---
_Source: https://npm.io/package/node-sass-custom-importer · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._
