chore(e2e): introduce TSC check (#3442)

Author: zdrapela

.github/workflows/e2e-tests-lint.yaml

@@ -13,29 +13,30 @@ on:
 
 jobs:
   lint:
-    name: ESLint and Prettier
+    name: TSC, ESLint and Prettier
     runs-on: ubuntu-latest
 
     steps:
       - name: Checkout
         uses: actions/checkout@v5
-        with:
-          sparse-checkout: |
-            e2e-tests
-            .nvmrc
-            .yarnrc.yml
-            .yarn
-            yarn.lock
 
       - name: Set up Node.js
         uses: actions/setup-node@v4
         with:
           node-version-file: ".nvmrc"
 
-      - name: Install dependencies
+      - name: Install dependencies root
+        working-directory: .
+        run: yarn install
+
+      - name: Install dependencies e2e-tests
         working-directory: ./e2e-tests
         run: yarn install --mode=skip-build
 
+      - name: Run TypeScript Compiler check
+        working-directory: ./e2e-tests
+        run: yarn tsc:check
+
       - name: Run ESLint check
         working-directory: ./e2e-tests
         run: yarn lint:check

docs/dynamic-plugins/debugging.md

@@ -25,9 +25,8 @@ Debugger listening on ws://127.0.0.1:9229/9299bb26-3c32-4781-9488-7759b8781db5
 ```
 
 * The application will be accessible from `http://localhost:7007`. You may start the front end by running the following command from the root directory: `yarn start --filter=app`. It will be available in `http://localhost:3000`
-<!-- markdown-link-check-disable -->
+<!-- markdown-link-check-disable-next-line -->
 * Attach your IDE debugger to the backend process. This step may depend on the IDE that you are using. For example, if you are using VS Code you may want to check [Node.js debugging in VS Code](https://code.visualstudio.com/docs/nodejs/nodejs-debugging)
-<!-- markdown-link-check-enable -->
 * Add Breakpoints to the files in folder `dynamic-plugins-root/${plugin-id}`. Optionally you can configure your IDE to add the source maps for the plugin so you can debug the TypeScript code directly and not the compiled JavaScript files
 
 ## Backend Dynamic Plugins Container Debug

docs/proxy.md

@@ -14,6 +14,7 @@ $ GLOBAL_AGENT_ENVIRONMENT_VARIABLE_NAMESPACE='' \
   yarn start
 ```
 
+<!-- markdown-link-check-disable-next-line -->
 You can use the command below to quickly start a local corporate proxy server (based on [Squid](https://www.squid-cache.org/)):
 
 ```shell
@@ -134,6 +135,7 @@ This approach simulates a corporate proxy environment in a Kubernetes/OpenShift
 
 1. Make sure the network plugin in your Kubernetes cluster supports network policies. [k3d](https://k3d.io) for example supports Network Policies out of the box.
 
+<!-- markdown-link-check-disable-next-line -->
 2. Create a separate proxy namespace, and deploy a [Squid](https://www.squid-cache.org/)-based proxy application there. The full URL to access the proxy server from within the cluster would be `http://squid-service.proxy.svc.cluster.local:3128`.
 
 ```shell
@@ -271,6 +273,7 @@ spec:
 
 ### OpenShift
 
+<!-- markdown-link-check-disable-next-line -->
 2. Create a separate proxy project, and deploy a [Squid](https://www.squid-cache.org/)-based proxy application there. The full URL to access the proxy server from within the cluster would be `http://squid-service.proxy.svc.cluster.local:3128`.
 
 ```shell

e2e-tests/.lintstagedrc.js

@@ -0,0 +1,8 @@
+/**
+ * @type {import('lint-staged').Configuration}
+ */
+export default {
+  "*": "yarn prettier:fix",
+  "*.{js,jsx,ts,tsx,mjs,cjs}": "yarn lint:fix",
+  "*.{ts,tsx}": () => "yarn tsc:check",
+};

e2e-tests/.lintstagedrc.json

@@ -23,6 +23,7 @@
     "lint:fix": "eslint . --ext .js,.ts --fix",
     "postinstall": "playwright install chromium",
     "tsc": "tsc",
+    "tsc:check": "tsc -p tsconfig.json",
     "prettier:check": "prettier --ignore-unknown --check .",
     "prettier:fix": "prettier --ignore-unknown --write ."
   },