fix: add webpack build step to CI test jobs

The extension's main entry point is dist/extension.js which requires
webpack to build. The test CI jobs were only running tsc (compile-tests)
but not webpack (compile), so the extension code wasn't being built
and tests were running against stale/missing code.

Also simplified the useEnvironmentsExtension check to only skip
activation when explicitly set to false by the user.

Author: eleanorjboyd

.github/workflows/pr-check.yml

@@ -102,6 +102,9 @@ jobs:
       - name: Install Dependencies
         run: npm ci
 
+      - name: Compile Extension
+        run: npm run compile
+
       - name: Compile Tests
         run: npm run compile-tests
 
@@ -148,6 +151,9 @@ jobs:
       - name: Install Dependencies
         run: npm ci
 
+      - name: Compile Extension
+        run: npm run compile
+
       - name: Compile Tests
         run: npm run compile-tests
 
@@ -194,6 +200,9 @@ jobs:
       - name: Install Dependencies
         run: npm ci
 
+      - name: Compile Extension
+        run: npm run compile
+
       - name: Compile Tests
         run: npm run compile-tests
 

src/extension.ts

@@ -99,11 +99,6 @@ export async function activate(context: ExtensionContext): Promise<PythonEnviron
                                inspection?.workspaceValue === false ||
                                inspection?.workspaceFolderValue === false;
 
-    // DEBUG: Log to stdout which will appear in CI logs
-    console.log('[python-envs] activate() called');
-    console.log('[python-envs] inspection:', JSON.stringify(inspection));
-    console.log('[python-envs] explicitlyDisabled:', explicitlyDisabled);
-    
     const useEnvironmentsExtension = !explicitlyDisabled;
     traceInfo(`Experiment Status: useEnvironmentsExtension setting set to ${useEnvironmentsExtension}`);
     if (!useEnvironmentsExtension) {