postcss-import - npm Package Versions

8.1.2 - 2016-05-07

• Fixed: prevent JSPM to throw unrecoverable error (#205)

8.1.1 - 2016-05-04

• Fixed: JSPM support (#194)

8.1.0 - 2016-04-04

• Added: JSPM browser field (#186)

8.0.2 - 2015-01-27

• Fixed: Comments between imports statements are ignored (#164)

8.0.1 - 2015-01-27

• Fixed: missing "lib" folder (#161)

8.0.0 - 2015-01-27

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")
  }
})

(#144)

• Removed: glob support (#146)

Globs can be implemented with custom resolve option

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

(#116)

• 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 _

7.1.3 - 2015-11-05

• Fixed: ensure node 0.12 compatibility, round 2 (#93)

7.1.2 - 2015-11-05

• Fixed: performance issue because of cloned options (#90)

7.1.1 - 2015-11-05

• Added: ensure node 0.12 compatibility