fix: Work around eslint globals config bug

ESLint have a weird behaviour that I would like to
categorize as a bug, but it's not really a bug, in where
using their API to get/create a config you get the
globals property as an object but their `CLIEngine`
class expects it to be an array.

I now convert the property from an object to an array before using the options.

eslint/eslint#7967

src/__tests__/index.js

@@ -193,6 +193,18 @@ const tests = [
       filePath: path.resolve("./test.md")
     },
     output: "# Foo\n\n_bar_"
+  },
+  {
+    title: "Test eslintConfig.globals as an object",
+    input: {
+      text: 'var foo = {  "bar": "baz"}',
+      eslintConfig: {
+        globals: {
+          someGlobal: true
+        }
+      }
+    },
+    output: 'var foo = { bar: "baz" };'
   }
 ];
 

src/index.js

@@ -63,6 +63,12 @@ function format(options) {
     getESLintConfig(filePath)
   );
 
+  if (typeof eslintConfig.globals === "object") {
+    eslintConfig.globals = Object.entries(eslintConfig.globals).map(
+      ([key, value]) => `${key}:${value}`
+    );
+  }
+
   const prettierOptions = merge(
     {},
     filePath && { filepath: filePath },