Fix up babel#172 (babel#177)

* Update two esprima tests to the new "expected TOKEN" messages * Update dynamic-import to use "expected (" error message
kristofdegrave · Oct 27, 2016 · ebda952 · ebda952
1 parent 4479bae
commit ebda952
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/src/parser/expression.js b/src/parser/expression.js
@@ -396,7 +396,7 @@ pp.parseExprAtom = function (refShorthandDefaultPos) {
       node = this.startNode();
       this.next();
       if (!this.match(tt.parenL)) {
-        this.unexpected();
+        this.unexpected(null, tt.parenL);
       }
       return this.finishNode(node, "Import");
 

diff --git a/test/fixtures/esprima/invalid-syntax/migrated_0112/options.json b/test/fixtures/esprima/invalid-syntax/migrated_0112/options.json
@@ -1,3 +1,3 @@
 {
   "throws": "Unexpected token, expected ; (1:2)"
-}
+}
diff --git a/test/fixtures/esprima/invalid-syntax/migrated_0114/options.json b/test/fixtures/esprima/invalid-syntax/migrated_0114/options.json
@@ -1,3 +1,3 @@
 {
   "throws": "Unexpected token, expected ; (1:2)"
-}
+}
diff --git a/test/fixtures/experimental/dynamic-import/direct-calls-only/options.json b/test/fixtures/experimental/dynamic-import/direct-calls-only/options.json
@@ -1,3 +1,3 @@
 {
-  "throws": "Unexpected token (2:15)"
+  "throws": "Unexpected token, expected ( (2:15)"
 }