Browse Source

node-compatibility, polyfilling Promise is node context as well

Herbert Vojčík 8 years ago
parent
commit
276f8d2f8a
4 changed files with 5 additions and 3 deletions
  1. 1 1
      bower.json
  2. 1 1
      config-node.js
  3. 1 1
      support/boot.js
  4. 2 0
      support/node-compatibility.js

+ 1 - 1
bower.json

@@ -15,6 +15,6 @@
     "tests"
   ],
   "devDependencies": {
-    "amber-compat-es2015": "^0.1.0"
+    "amber-compat-es2015": "^0.1.1"
   }
 }

+ 1 - 1
config-node.js

@@ -3,5 +3,5 @@
 // Free to edit. You can break tests (cli test runner uses
 // this to build itself - it is a node executable).
 define("amber/Platform", ["amber_core/Platform-Node"], {});
-define("amber/browser-compatibility", {});
+define("amber/compatibility", ["amber/node-compatibility"], {});
 define("jquery", {});

+ 1 - 1
support/boot.js

@@ -39,7 +39,7 @@
 
 //jshint eqnull:true
 
-define(['require', './browser-compatibility'], function (require) {
+define(['require', './compatibility'], function (require) {
 
     /* Reconfigurable micro composition system, https://github.com/amber-smalltalk/brikz */
 

+ 2 - 0
support/node-compatibility.js

@@ -0,0 +1,2 @@
+// This file is injected dependencies by amber-compat-xxx modules.
+// Therefore it is important that it _does_not_have_ define call.