node package manager

postcss-import

PostCSS plugin to import CSS files

postcss-import

PostCSS plugin to transform @import rules by inlining content.

This plugin can consume local files, node modules or web_modules. To resolve path of an @import rule, it can look into root directory (by default process.cwd()), web_modules, node_modules or local modules. When importing a module, it will look for index.css or file referenced in package.json in the style or main fields. You can also provide manually multiples paths where to look at.

Notes:

  • This plugin should probably be used as the first plugin of your list. This way, other plugins will work on the AST as if there were only a single file to process, and will probably work as you can expect.
  • This plugin works great with postcss-url plugin, which will allow you to adjust assets url() (or even inline them) after inlining imported files.
  • In order to optimize output, this plugin will only import a file once on a given scope (root, media query...). Tests are made from the path & the content of imported files (using a hash table). If this behavior is not what you want, look at skipDuplicates option
  • If you are looking for glob, or sass like imports (prefixed partials), please look at postcss-easy-import (which use this plugin under the hood).
  • This plugin attempts to follow the CSS @import spec; @import statements must precede all other statements (besides @charset).
$ npm install postcss-import

If your stylesheets are not in the same place where you run postcss (process.cwd()), you will need to use from option to make relative imports work from input dirname.

// dependencies 
var fs = require("fs")
var postcss = require("postcss")
var atImport = require("postcss-import")
 
// css to be processed 
var css = fs.readFileSync("css/input.css", "utf8")
 
// process css 
postcss()
  .use(atImport())
  .process(css, {
    // `from` option is required so relative import can work from input dirname 
    from: "css/input.css"
  })
  .then(function (result) {
    var output = result.css
 
    console.log(output)
  })

Using this input.css:

/* can consume `node_modules`, `web_modules` or local modules */
@import "cssrecipes-defaults"/* == @import "./node_modules/cssrecipes-defaults/index.css"; */
@import "normalize.css"/* == @import "./node_modules/normalize.css/normalize.css"; */
 
@import "css/foo.css"/* relative to stylesheets/ according to `from` option above */
 
@import "css/bar.css" (min-width: 25em);
 
body {
  background: black;
}

will give you:

/* ... content of ./node_modules/cssrecipes-defaults/index.css */
/* ... content of ./node_modules/normalize.css/normalize.css */
 
/* ... content of foo.css */
 
@media (min-width: 25em) {
/* ... content of bar.css */
}
 
body {
  background: black;
}

Checkout tests for more examples.

Type: String
Default: process.cwd() or dirname of the postcss from

Define the root where to resolve path (eg: place where node_modules are). Should not be used that much.
Note: nested @import will additionally benefit of the relative dirname of imported files.

Type: String|Array
Default: []

A string or an array of paths in where to look for files.

Type: Array
Default: undefined

An array of plugins to be applied on each imported files.

Type: Function
Default: null

Function called after the import process. Take one argument (array of imported files).

Type: Function
Default: null

You can provide a custom path resolver with this option. This function gets (id, basedir, importOptions) arguments and should return a path, an array of paths or a promise resolving to the path(s). If you do not return an absolute path, your path will be resolved to an absolute path using the default resolver. You can use resolve for this.

Type: Function
Default: null

You can overwrite the default loading way by setting this option. This function gets (filename, importOptions) arguments and returns content or promised content.

Type: Boolean
Default: true

By default, similar files (based on the same content) are being skipped. It's to optimize output and skip similar files like normalize.css for example. If this behavior is not what you want, just set this option to false to disable it.

Type: Object
Default: null

DEPRECATED. If you are using postcss-import v8.2.0 & postcss-loader v1.0.0 or later, this is unnecessary.

An object with addDependency() method, taking file path as an argument. Called whenever a file is imported. You can use it for hot-reloading in webpack postcss-loader like this:

postcss: function(webpack) {
  return [
    require('postcss-import')({
      addDependencyTo: webpack
      /* Is equivalent to
      onImport: function (files) {
        files.forEach(this.addDependency)
      }.bind(webpack)
      */
    })
  ]
}
var postcss = require("postcss")
var atImport = require("postcss-import")
 
postcss()
  .use(atImport({
    path: ["src/css"],
    transform: require("css-whitespace")
  }))
  .process(cssString)
  .then(function (result) {
    var css = result.css
  })

postcss-import can @import jspm dependencies if pkg-resolve is installed by the user. Run npm install pkg-resolve to install it. postcss-import should then be able to import from jspm dependencies without further configuration.

postcss-import adds a message to result.messages for each @import. Messages are in the following format:

{
  type: 'dependency',
  file: absoluteFilePath,
  parent: fileContainingTheImport
}

This is mainly for use by postcss runners that implement file watching.


  • ⇄ Pull requests and ★ Stars are always welcome.
  • For bugs and feature requests, please create an issue.
  • Pull requests must be accompanied by passing automated tests ($ npm test).

Changelog

License