From f78e6302b4e4a8363ee312b6db814b480376be3b Mon Sep 17 00:00:00 2001
From: Carl-Erik Kopseng <carlerik@gmail.com>
Date: Fri, 20 Oct 2023 15:47:10 +0200
Subject: [PATCH] Remove Circle CI setup

---
 docker-compose.yml | 29 -----------------------------
 1 file changed, 29 deletions(-)
 delete mode 100644 docker-compose.yml

diff --git a/docker-compose.yml b/docker-compose.yml
deleted file mode 100644
index 90ea665ab..000000000
--- a/docker-compose.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-# Docker Compose setup file
-# Purpose: testbed for changes to Circle CI setup
-# Usage: `docker-compose up`
-version: "3"
-services:
-  node:
-    image: "circleci/node:10.15.1-browsers"
-    user: "root"
-    working_dir: /home/node/app
-
-    # use the one built-in to the image to avoid potential issues like
-    # https://github.com/GoogleChrome/puppeteer/issues/3774
-    # This variable is used by all scripts - including the `test-esm-bundle`
-    environment:
-      PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: "true"
-      SINON_CHROME_BIN: /usr/bin/google-chrome-stable
-    volumes:
-      # This mounts the local directory - saving `npm install`
-      - ./:/home/node/app
-
-    # There are differences between Circle CI and Docker `command`,
-    # forcing us to do this little workaround
-    command: >
-      sh -c " $$SINON_CHROME_BIN --version
-      && npm run test-headless -- --chrome $$SINON_CHROME_BIN --allow-chrome-as-root
-      && npm run test-webworker -- --chrome $$SINON_CHROME_BIN --allow-chrome-as-root
-      && npm run check-esm-bundle-runs-in-browser
-      && npm run test-node
-      "