Update Next.js to v16.2.4 by Copilot · Pull Request #250 · infosupport/tech-survey

Copilot · 2026-04-24T11:49:35Z

Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/37286d08-3645-490c-9db4-2e09342cc6ad Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

nicojs · 2026-04-25T12:58:40Z

@copilot please fix the linting warning

… rename middleware to proxy Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/d87ecba7-3770-462f-b93d-5831c3334381 Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot · 2026-04-25T13:04:34Z

@copilot please fix the linting warning

Fixed in a6a2202. Three things were addressed:

tsconfig.json jsx changed from preserve to react-jsx — Next.js 16 requires the React automatic JSX runtime, which caused the build to fail with 'React' is declared but its value is never read errors due to noUnusedLocals: true.
Removed unnecessary import React in 8 files — With the react-jsx transform, React no longer needs to be explicitly imported for JSX. Also replaced React.useState with a named useState import in show-data-table.tsx.
Renamed middleware.ts → proxy.ts — Fixes the ⚠ The "middleware" file convention is deprecated. Please use "proxy" instead. build warning.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

checkpoint.prisma.io
- Triggering command: /usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/tech-survey/tech-survey/node_modules/prisma/build/child {"product":"prisma","version":"5.22.0","cli_install_type":"local","information":"","local_timestamp":"2026-04-25T12:59:30Z","project_hash":"14632b08","cli_path":"/home/REDACTED/work/tech-survey/tech-survey/node_modules/prisma/build/index.js","cli_path_hash" --64 (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

nicojs · 2026-04-25T13:19:11Z

@copilot The tests are failing. Any idea why? Can you fix them?

Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/831c49c3-8edc-4cab-b378-a6143098e847 Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot · 2026-04-25T14:09:16Z

@copilot The tests are failing. Any idea why? Can you fix them?

Fixed in be839fe.

The root cause: the Next.js 16 middleware template resolves the handler as mod.middleware || mod.default — it does not check mod.proxy. When I renamed the export from middleware to proxy in src/proxy.ts, the handler resolved to undefined, causing the proxy to fail silently and leave every session as null (unprotected routes showed no session; protected routes fell through to the Microsoft OAuth redirect, which can't load in CI, producing the "This page couldn't load" browser error).

The fix keeps the file named proxy.ts (satisfying the Next.js 16 convention and removing the deprecation warning) while exporting the function as middleware so the template can find it.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

checkpoint.prisma.io
- Triggering command: /usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/tech-survey/tech-survey/node_modules/prisma/build/child {"product":"prisma","version":"5.22.0","cli_install_type":"local","information":"","local_timestamp":"2026-04-25T13:22:28Z","project_hash":"14632b08","cli_path":"/home/REDACTED/work/tech-survey/tech-survey/node_modules/prisma/build/index.js","cli_path_hash" --64 (dns block)
- Triggering command: /usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/tech-survey/tech-survey/node_modules/prisma/build/child {"product":"prisma","version":"5.22.0","cli_install_type":"local","information":"","local_timestamp":"2026-04-25T13:50:58Z","project_hash":"14632b08","cli_path":"/home/REDACTED/work/tech-survey/tech-survey/node_modules/.bin/prisma","cli_path_hash":"faf26618 grep -l e\|auth.*secret.*edge s rgo/bin/grep *edge ins/postcss-url--l rgo/bin/grep grep -l e\|auth.*secret.*edge ace/helpers.js /home/REDACTED/.local/bin/grep *edge -error-loader.js-F /home/REDACTED/.lo-L grep (dns block)
fonts.googleapis.com
- Triggering command: /usr/local/bin/node node /home/REDACTED/work/tech-survey/tech-survey/node_modules/.bin/next build grep -l e\|auth.*secret.*edge ete.js p/bin/grep *edge /src/index.js p/bin/grep grep -l e\|auth.*secret.*edge edback.js cal/bin/grep *edge lur.js cal/bin/grep grep (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

nicojs · 2026-04-27T08:16:32Z

@copilot The next.js website says is should be named proxy, see https://nextjs.org/docs/app/getting-started/proxy

nicojs · 2026-04-27T08:20:33Z

    /// outside of this class except in `auth.ts`.
    // @ts-expect-error - Used in src/auth.ts
    private toPrismaAdapter() {
+        // eslint-disable-next-line @typescript-eslint/no-unnecessary-type-assertion


Remove the assertion instead

Done in 88f1691 — removed the as Adapter cast and the eslint-disable comment above it.

nicojs · 2026-04-27T08:21:15Z

This file should export proxy instead of middleware.

Fixed in 88f1691 — src/proxy.ts now exports proxy.

nicojs · 2026-04-27T08:22:56Z

        "module": "ESNext",
        "moduleResolution": "Bundler",
-        "jsx": "preserve",
+        "jsx": "react-jsx",


Why this change?

Next.js 16 requires the React automatic JSX runtime (react-jsx) and will reject preserve. With "jsx": "preserve" and "noUnusedLocals": true, the TypeScript compiler reported 'React' is declared but its value is never read for every file that had import React from "react" — because the JSX transform no longer needs an explicit React import. Changing to "react-jsx" (and removing those imports) fixes both issues.

…assertion Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/c9ba8981-4324-454b-b50a-102389bba67f Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot · 2026-04-27T08:32:53Z

@copilot The next.js website says is should be named proxy, see https://nextjs.org/docs/app/getting-started/proxy

Fixed in 88f1691. The Turbopack build error confirmed this: Proxy is missing expected function export name — Ensure this file has either a default or "proxy" function export. The export is now proxy as the docs require.

nicojs · 2026-04-27T12:28:20Z

@copilot please fix the tests. 3 are failing.

Build output

▲ Next.js 16.2.4
- Local:         http://localhost:36047
- Network:       http://10.1.1.145:36047/
✓ Ready in 136ms
▲ Next.js 16.2.4
- Local:         http://localhost:45807
- Network:       http://10.1.1.145:45807/
✓ Ready in 149ms
  ✘   2 [chromium] › tests/test.spec.ts:54:5 › Desktop tests using a single role › Check if the default role(s) are set (0ms)
  -   3 [chromium] › tests/test.spec.ts:65:5 › Desktop tests using a single role › Answer questions of a single role
  -   4 [chromium] › tests/test.spec.ts:85:5 › Desktop tests using a single role › Forget to fill in a question
  -   5 [chromium] › tests/test.spec.ts:115:5 › Desktop tests using a single role › Fill in the survey and show you are present on the anonymous results
  -   6 [chromium] › tests/test.spec.ts:141:5 › Desktop tests using a single role › Fill in the survey and show you are present on the find-the-expert page
  -   7 [chromium] › tests/test.spec.ts:193:5 › Desktop tests using a multiple roles › Create multiple questions and assign specific roles
  -   8 [chromium] › tests/test.spec.ts:206:5 › Desktop tests using a multiple roles › if questions are visible in roles
  -   9 [chromium] › tests/test.spec.ts:222:5 › Desktop tests using a multiple roles › Answer questions of multiple roles
  ✘   1 [chromium] › tests/find-the-expert-tests.spec.ts:42:5 › Desktop tests › Navigate to tech-page without results (5.9s)
(node:6782) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
(Use `node --trace-deprecation ...` to show where the warning was created)

> is-survey@0.1.0 start
> node ./node_modules/next/dist/bin/next start --port 0

▲ Next.js 16.2.4
- Local:         http://localhost:33017
- Network:       http://10.1.1.145:33017/
✓ Ready in 124ms
  ✘  10 [android] › tests/test.spec.ts:273:5 › Mobile tests using a single role › (Mobile) Check if the default role(s) are set (0ms)
  -  11 [android] › tests/test.spec.ts:284:5 › Mobile tests using a single role › (Mobile) Answer questions of a single role
  -  12 [android] › tests/test.spec.ts:301:5 › Mobile tests using a single role › (Mobile) Forget to fill in a question
  -  13 [android] › tests/test.spec.ts:328:5 › Mobile tests using a single role › (Mobile) Fill in the survey and show you are present on the find-the-expert page
  -  14 [android] › tests/test.spec.ts:362:5 › Mobile tests using a single role › (Mobile) Fill in the survey and show you are present on the anonymous results
  -  15 [android] › tests/test.spec.ts:397:5 › Mobile tests using multiple roles › (Mobile) Create multiple questions and assign specific roles
  -  16 [android] › tests/test.spec.ts:410:5 › Mobile tests using multiple roles › (Mobile) if questions are visible in roles
  -  17 [android] › tests/test.spec.ts:418:5 › Mobile tests using multiple roles › (Mobile) Answer questions of multiple roles


  1) [chromium] › tests/find-the-expert-tests.spec.ts:42:5 › Desktop tests › Navigate to tech-page without results 

    Error: expect(locator).toBeVisible() failed

    Locator: getByText('Find by tech')
    Expected: visible
    Timeout: 5000ms
    Error: element(s) not found

    Call log:
      - Expect "toBeVisible" with timeout 5000ms
      - waiting for getByText('Find by tech')


       at find-the-expert-page.ts:16

      14 |     async navigateToLandingPage() {
      15 |         await this.page.goto(`http://localhost:${this.port}/find-the-expert`);
    > 16 |         await expect(this.page.getByText("Find by tech")).toBeVisible();
         |                                                           ^
      17 |     }
      18 | }
      19 |
        at FindTheExpertPage.navigateToLandingPage (/home/runner/work/tech-survey/tech-survey/tests/find-the-expert-page.ts:16:59)
        at /home/runner/work/tech-survey/tech-survey/tests/find-the-expert-tests.spec.ts:35:9

    Error Context: test-results/find-the-expert-tests-Desk-7e070-o-tech-page-without-results-chromium/error-context.md

  2) [chromium] › tests/test.spec.ts:54:5 › Desktop tests using a single role › Check if the default role(s) are set 

    Error: expect(locator).toBeVisible() failed

    Locator: getByRole('heading', { name: 'Select Roles' })
    Expected: visible
    Timeout: 5000ms
    Error: element(s) not found

    Call log:
      - Expect "toBeVisible" with timeout 5000ms
      - waiting for getByRole('heading', { name: 'Select Roles' })


       at survey-page.ts:20

      18 |                 name: "Select Roles",
      19 |             }),
    > 20 |         ).toBeVisible();
         |           ^
      21 |     }
      22 |
      23 |     async checkUrl(path: string) {
        at SurveyPage.navigateToLandingPage (/home/runner/work/tech-survey/tech-survey/tests/survey-page.ts:20:11)
        at /home/runner/work/tech-survey/tech-survey/tests/test.spec.ts:33:5

    Error Context: test-results/test-Desktop-tests-using-a-65f3d--the-default-role-s-are-set-chromium/error-context.md

  3) [android] › tests/test.spec.ts:273:5 › Mobile tests using a single role › (Mobile) Check if the default role(s) are set 

    Error: expect(locator).toBeVisible() failed

    Locator: getByRole('heading', { name: 'Select Roles' })
    Expected: visible
    Timeout: 5000ms
    Error: element(s) not found

    Call log:
      - Expect "toBeVisible" with timeout 5000ms
      - waiting for getByRole('heading', { name: 'Select Roles' })


       at survey-page.ts:20

      18 |                 name: "Select Roles",
      19 |             }),
    > 20 |         ).toBeVisible();
         |           ^
      21 |     }
      22 |
      23 |     async checkUrl(path: string) {
        at SurveyPage.navigateToLandingPage (/home/runner/work/tech-survey/tech-survey/tests/survey-page.ts:20:11)
        at /home/runner/work/tech-survey/tech-survey/tests/test.spec.ts:33:5

    Error Context: test-results/test-Mobile-tests-using-a--4f7d4--the-default-role-s-are-set-android/error-context.md

  3 failed
    [chromium] › tests/find-the-expert-tests.spec.ts:42:5 › Desktop tests › Navigate to tech-page without results 
    [chromium] › tests/test.spec.ts:54:5 › Desktop tests using a single role › Check if the default role(s) are set 
    [android] › tests/test.spec.ts:273:5 › Mobile tests using a single role › (Mobile) Check if the default role(s) are set 
  14 did not run▲ Next.js 16.2.4
- Local:         http://localhost:36047
- Network:       http://10.1.1.145:36047/
✓ Ready in 136ms
▲ Next.js 16.2.4
- Local:         http://localhost:45807
- Network:       http://10.1.1.145:45807/
✓ Ready in 149ms
  ✘   2 [chromium] › tests/test.spec.ts:54:5 › Desktop tests using a single role › Check if the default role(s) are set (0ms)
  -   3 [chromium] › tests/test.spec.ts:65:5 › Desktop tests using a single role › Answer questions of a single role
  -   4 [chromium] › tests/test.spec.ts:85:5 › Desktop tests using a single role › Forget to fill in a question
  -   5 [chromium] › tests/test.spec.ts:115:5 › Desktop tests using a single role › Fill in the survey and show you are present on the anonymous results
  -   6 [chromium] › tests/test.spec.ts:141:5 › Desktop tests using a single role › Fill in the survey and show you are present on the find-the-expert page
  -   7 [chromium] › tests/test.spec.ts:193:5 › Desktop tests using a multiple roles › Create multiple questions and assign specific roles
  -   8 [chromium] › tests/test.spec.ts:206:5 › Desktop tests using a multiple roles › if questions are visible in roles
  -   9 [chromium] › tests/test.spec.ts:222:5 › Desktop tests using a multiple roles › Answer questions of multiple roles
  ✘   1 [chromium] › tests/find-the-expert-tests.spec.ts:42:5 › Desktop tests › Navigate to tech-page without results (5.9s)
(node:6782) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
(Use `node --trace-deprecation ...` to show where the warning was created)

> is-survey@0.1.0 start
> node ./node_modules/next/dist/bin/next start --port 0

▲ Next.js 16.2.4
- Local:         http://localhost:33017
- Network:       http://10.1.1.145:33017/
✓ Ready in 124ms
  ✘  10 [android] › tests/test.spec.ts:273:5 › Mobile tests using a single role › (Mobile) Check if the default role(s) are set (0ms)
  -  11 [android] › tests/test.spec.ts:284:5 › Mobile tests using a single role › (Mobile) Answer questions of a single role
  -  12 [android] › tests/test.spec.ts:301:5 › Mobile tests using a single role › (Mobile) Forget to fill in a question
  -  13 [android] › tests/test.spec.ts:328:5 › Mobile tests using a single role › (Mobile) Fill in the survey and show you are present on the find-the-expert page
  -  14 [android] › tests/test.spec.ts:362:5 › Mobile tests using a single role › (Mobile) Fill in the survey and show you are present on the anonymous results
  -  15 [android] › tests/test.spec.ts:397:5 › Mobile tests using multiple roles › (Mobile) Create multiple questions and assign specific roles
  -  16 [android] › tests/test.spec.ts:410:5 › Mobile tests using multiple roles › (Mobile) if questions are visible in roles
  -  17 [android] › tests/test.spec.ts:418:5 › Mobile tests using multiple roles › (Mobile) Answer questions of multiple roles


  1) [chromium] › tests/find-the-expert-tests.spec.ts:42:5 › Desktop tests › Navigate to tech-page without results 

    Error: expect(locator).toBeVisible() failed

    Locator: getByText('Find by tech')
    Expected: visible
    Timeout: 5000ms
    Error: element(s) not found

    Call log:
      - Expect "toBeVisible" with timeout 5000ms
      - waiting for getByText('Find by tech')


       at find-the-expert-page.ts:16

      14 |     async navigateToLandingPage() {
      15 |         await this.page.goto(`http://localhost:${this.port}/find-the-expert`);
    > 16 |         await expect(this.page.getByText("Find by tech")).toBeVisible();
         |                                                           ^
      17 |     }
      18 | }
      19 |
        at FindTheExpertPage.navigateToLandingPage (/home/runner/work/tech-survey/tech-survey/tests/find-the-expert-page.ts:16:59)
        at /home/runner/work/tech-survey/tech-survey/tests/find-the-expert-tests.spec.ts:35:9

    Error Context: test-results/find-the-expert-tests-Desk-7e070-o-tech-page-without-results-chromium/error-context.md

  2) [chromium] › tests/test.spec.ts:54:5 › Desktop tests using a single role › Check if the default role(s) are set 

    Error: expect(locator).toBeVisible() failed

    Locator: getByRole('heading', { name: 'Select Roles' })
    Expected: visible
    Timeout: 5000ms
    Error: element(s) not found

    Call log:
      - Expect "toBeVisible" with timeout 5000ms
      - waiting for getByRole('heading', { name: 'Select Roles' })


       at survey-page.ts:20

      18 |                 name: "Select Roles",
      19 |             }),
    > 20 |         ).toBeVisible();
         |           ^
      21 |     }
      22 |
      23 |     async checkUrl(path: string) {
        at SurveyPage.navigateToLandingPage (/home/runner/work/tech-survey/tech-survey/tests/survey-page.ts:20:11)
        at /home/runner/work/tech-survey/tech-survey/tests/test.spec.ts:33:5

    Error Context: test-results/test-Desktop-tests-using-a-65f3d--the-default-role-s-are-set-chromium/error-context.md

  3) [android] › tests/test.spec.ts:273:5 › Mobile tests using a single role › (Mobile) Check if the default role(s) are set 

    Error: expect(locator).toBeVisible() failed

    Locator: getByRole('heading', { name: 'Select Roles' })
    Expected: visible
    Timeout: 5000ms
    Error: element(s) not found

    Call log:
      - Expect "toBeVisible" with timeout 5000ms
      - waiting for getByRole('heading', { name: 'Select Roles' })


       at survey-page.ts:20

      18 |                 name: "Select Roles",
      19 |             }),
    > 20 |         ).toBeVisible();
         |           ^
      21 |     }
      22 |
      23 |     async checkUrl(path: string) {
        at SurveyPage.navigateToLandingPage (/home/runner/work/tech-survey/tech-survey/tests/survey-page.ts:20:11)
        at /home/runner/work/tech-survey/tech-survey/tests/test.spec.ts:33:5

    Error Context: test-results/test-Mobile-tests-using-a--4f7d4--the-default-role-s-are-set-android/error-context.md

  3 failed
    [chromium] › tests/find-the-expert-tests.spec.ts:42:5 › Desktop tests › Navigate to tech-page without results 
    [chromium] › tests/test.spec.ts:54:5 › Desktop tests using a single role › Check if the default role(s) are set 
    [android] › tests/test.spec.ts:273:5 › Mobile tests using a single role › (Mobile) Check if the default role(s) are set 
  14 did not run

Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/4e47653f-e14f-440b-86cf-c729506f9ad0 Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot · 2026-04-27T13:17:24Z

@copilot please fix the tests. 3 are failing.

Build output

...

Fixed in bba8921.

Root cause: In Next.js 16, src/proxy.ts was exporting auth from ~/auth, which transitively imports @prisma/client. The proxy runs in the Edge Runtime sandbox, where only a limited set of native modules is allowed — @prisma/client is not one of them, so it threw TypeError: Native module not found. This caused the proxy to fail on initialization, so every request appeared unauthenticated.

Fix: Extracted src/auth.config.ts as a lightweight, Edge Runtime-compatible base config (no Prisma, no Node.js-only imports). Updated src/proxy.ts to call NextAuth(authConfig) using this base config. Updated src/auth.ts to spread authConfig and extend it with the Prisma adapter and Microsoft Entra ID provider (these only run in Node.js server components and API routes, where Prisma works fine).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

authjs.dev
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
checkpoint.prisma.io
- Triggering command: /usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/tech-survey/tech-survey/node_modules/prisma/build/child {"product":"prisma","version":"5.22.0","cli_install_type":"local","information":"","local_timestamp":"2026-04-27T13:14:34Z","project_hash":"14632b08","cli_path":"/home/REDACTED/work/tech-survey/tech-survey/node_modules/prisma/build/index.js","cli_path_hash" --64 -E o\|x-forwarded-h-I ude rgo/bin/bash (dns block)
nextjs.org
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Initial plan

ea16d15

Copilot AI assigned Copilot and nicojs Apr 24, 2026

Copilot started work on behalf of nicojs April 24, 2026 11:49 View session

Copilot AI linked an issue Apr 24, 2026 that may be closed by this pull request

Update to latest next.js release #249

Open

chore: update Next.js to v16.2.4 with ESLint flat config migration

28d4fef

Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/37286d08-3645-490c-9db4-2e09342cc6ad Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Update to latest next.js release~~ Update Next.js to v16.2.4 Apr 24, 2026

Copilot AI requested a review from nicojs April 24, 2026 12:12

Copilot finished work on behalf of nicojs April 24, 2026 12:12

nicojs marked this pull request as ready for review April 25, 2026 12:33

nicojs approved these changes Apr 25, 2026

View reviewed changes

Copilot started work on behalf of nicojs April 25, 2026 12:58 View session

fix: align tsconfig jsx with Next.js 16, remove unused React imports,…

a6a2202

… rename middleware to proxy Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/d87ecba7-3770-462f-b93d-5831c3334381 Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot AI requested a review from nicojs April 25, 2026 13:05

Copilot finished work on behalf of nicojs April 25, 2026 13:05

Copilot started work on behalf of nicojs April 25, 2026 13:19 View session

fix: export auth as middleware (not proxy) from src/proxy.ts

be839fe

Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/831c49c3-8edc-4cab-b378-a6143098e847 Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot finished work on behalf of nicojs April 25, 2026 14:09

nicojs requested changes Apr 27, 2026

View reviewed changes

Copilot started work on behalf of nicojs April 27, 2026 08:23 View session

fix: export auth as proxy from src/proxy.ts; remove unnecessary type …

88f1691

…assertion Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/c9ba8981-4324-454b-b50a-102389bba67f Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot AI requested a review from nicojs April 27, 2026 08:34

Copilot finished work on behalf of nicojs April 27, 2026 08:34

nicojs approved these changes Apr 27, 2026

View reviewed changes

Copilot started work on behalf of nicojs April 27, 2026 12:28 View session

fix: split auth config to be Edge Runtime-compatible, fix tests

bba8921

Agent-Logs-Url: https://github.com/infosupport/tech-survey/sessions/4e47653f-e14f-440b-86cf-c729506f9ad0 Co-authored-by: nicojs <1828233+nicojs@users.noreply.github.com>

Copilot finished work on behalf of nicojs April 27, 2026 13:18

Copilot AI requested a review from nicojs April 27, 2026 13:18

Uh oh!

Conversation

Copilot AI commented Apr 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nicojs commented Apr 25, 2026

Uh oh!

Copilot AI commented Apr 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

nicojs commented Apr 25, 2026

Uh oh!

Copilot AI commented Apr 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

nicojs commented Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nicojs Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

nicojs Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

nicojs Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Apr 27, 2026

Uh oh!

nicojs commented Apr 27, 2026

Uh oh!

Copilot AI commented Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Apr 24, 2026 •

edited

Loading

Copilot AI commented Apr 25, 2026 •

edited

Loading

Copilot AI commented Apr 25, 2026 •

edited

Loading

nicojs commented Apr 27, 2026 •

edited

Loading

Copilot AI commented Apr 27, 2026 •

edited

Loading