From 68aad8b205dd3fc2e71771c3a008ce3fa5e2c106 Mon Sep 17 00:00:00 2001
From: William Chargin <wchargin@gmail.com>
Date: Tue, 13 Aug 2019 09:41:45 -0700
Subject: [PATCH] Remove non-standard bare-`catch` blocks (#1281)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Summary:
In ES6, the [`try` statement grammar][1] requires a catch parameter; the
parameter is only optional in the latest draft of ECMAScript, which is
of course not yet ratified as any actual standard.

Even though we don’t officially pledge to support Node 8, this is
currently the only breakage, and it’s easy enough to fix.

[1]: https://www.ecma-international.org/ecma-262/6.0/#sec-try-statement

Test Plan:
Running `yarn start` on Node v8.11.4 no longer raises a syntax error.

wchargin-branch: catch-parameter
---
 src/core/_getProjectIds.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/core/_getProjectIds.js b/src/core/_getProjectIds.js
index f045abb..abca173 100644
--- a/src/core/_getProjectIds.js
+++ b/src/core/_getProjectIds.js
@@ -26,7 +26,7 @@ module.exports = async function getProjectIds(
   let entries = [];
   try {
     entries = await fs.readdir(projectsPath);
-  } catch {
+  } catch (e) {
     return [];
   }
   const getProjectId = async (entry) => {
@@ -34,7 +34,7 @@ module.exports = async function getProjectIds(
       const jsonPath = path.join(projectsPath, entry, "project.json");
       await fs.stat(jsonPath);
       return base64url.decode(entry);
-    } catch {
+    } catch (e) {
       return null;
     }
   };