Releases · postcss/postcss-import

All imports statements must be at the top of your file now, per CSS specification.
You should use postcss-reporter to see the warnings raised.

Removed: async mode/option (now async by default)
(#107)
Removed: "bower_components" not supported by default anymore,
use "path" option to add it back
Removed: encoding option. Encoding can be specified in custom load option

postcssImport({
  load: function(filename) {
    return fs.readFileSync(filename, "utf-8")
  }
})

Globs can be implemented with custom resolve option

postcssImport({
  resolve: function(id, base) {
    return glob.sync(path.join(base, id))
  }
})

Changed: custom resolve has more responsibility for paths resolving.
See resolve option
for more information about this change
(#116)
Changed: support promise in transform option and undefined result will be
skipped
(#147)
Changed: options.plugins are applied to unprocessed ast before imports
detecting
(157)
Added: custom resolve function can return array of paths
(#120)
Added: custom syntax in imported files support
(#130)
Added: support custom load option
(#144)
Added: detect css extension in package.json main field
(153)

Note:
_If you miss options/default behavior (glob etc), a new plugin will handle all
those things.
Please follow issue #145
_

Provide feedback