Fixed: plugin can be consumed correctly from es5 environment (2.0.1)

Author: MoOx

CHANGELOG.md

@@ -1,3 +1,8 @@
+# 2.0.1 - 2015-09-14
+
+- Fixed: plugin can be consumed correctly from es5 environment
+([#11](https://github.com/cssnext/postcss-cssnext/issues/11))
+
 # 2.0.0 - 2015-09-14
 
 - Added: support for PostCSS v5.x

package.json

@@ -1,6 +1,6 @@
 {
   "name": "postcss-cssnext",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "Use tomorrow's CSS syntax, today",
   "keywords": [
     "css",

src/index.js

@@ -4,9 +4,7 @@ import { isSupported } from "caniuse-api"
 import libraryFeatures from "./features"
 import featuresActivationMap from "./features-activation-map"
 
-export { libraryFeatures as features }
-
-export default postcss.plugin("postcss-cssnext", (options) => {
+const plugin = postcss.plugin("postcss-cssnext", (options) => {
   options = {
     features: {},
     // options.browsers is deliberately undefined by default to inherit
@@ -68,3 +66,15 @@ export default postcss.plugin("postcss-cssnext", (options) => {
 
   return processor
 })
+
+// according to the way babel transpile es6 module
+// we cannot use the following syntax to export features
+//
+// export { libraryFeatures as features }
+//
+// babel only add `module.exports = exports["default"];` if there is only one
+// thing exported
+// so we add `features` as a plugin property
+plugin.features = libraryFeatures
+
+export default plugin