ci: make e2e tests run on a production-like install

to reproduce exact dependency versions

.github/workflows/reusable-e2e-tests.yml

@@ -38,13 +38,8 @@ jobs:
           cache: yarn
           cache-dependency-path: yarn.lock
 
-      # We install project dependencies to be able to run e2e-launcher.js
-      - run: yarn install --frozen-lockfile
-
       # But we do install log4brains from the registry
       - run: npm install -g ${{ inputs.npm-package-fullname }}
 
-      # We don't use "yarn e2e" directly so we are sure that we are using the global version of log4brains
       - name: E2E Tests on the registry version
-        run: node e2e-launcher.js
-        working-directory: e2e-tests
+        run: yarn e2e

.github/workflows/reusable-tests.yml

@@ -65,4 +65,6 @@ jobs:
         run: |
           yarn link-cli
           echo "$(yarn global bin)" >> $GITHUB_PATH
+          rm -rf node_modules
+          yarn install --production --no-lockfile
           yarn e2e

CONTRIBUTING.md

@@ -78,6 +78,13 @@ Log4brains follows a **simplified Git Flow** model. Here’s how the process wor
    yarn format:fix   # enforced automatically before every commit with husky+lint-staged
    yarn typescript   # enforced automatically before every commit with husky
    yarn test:changed # (or `yarn test` to run all the tests)
+
+   # Simulate the execution on a fresh install:
+   yarn link-cli
+   yarn build
+   rm -rf node_modules
+   yarn install --production --no-lockfile
+   yarn e2e
    ```
 
    If applicable, a pull request without tests will be rejected.

e2e-tests/package.json

@@ -0,0 +1,11 @@
+{
+  "name": "e2e-tests",
+  "description": "Log4brains E2E tests sub-package",
+  "private": true,
+  "devDependencies": {
+    "chai": "^4.2.0",
+    "chalk": "^4.1.0",
+    "execa": "^4.1.0",
+    "rimraf": "^6.0.1"
+  }
+}