chore: upgrade to React 19, Next.js 16, Apollo Client 4, Apollo Server 5 by Soxasora · Pull Request #2904 · stackernews/stacker.news

Soxasora · 2026-04-05T14:32:34Z

Description

This PR aims at upgrading Next.js from 14 to 16.
Other than performance gains, the most recent reason to update is the introduction of the Node.js Proxy (ex-middleware), enabling custom domains (#2897) db lookup right inside the proxy, without needing an API endpoint to do so.

Upgrades

Next.js 14.2.25 -> 16.2.2
- node.js middleware/proxy by default
React 18.3.1 -> 19.2.4
- required by Next.js 16 and recommended by Lexical
GraphQL 16.9.0 -> 16.13.2
- required by Apollo
Apollo Client 3.11.8 -> 4.1.6
- React 19 support
Apollo Server 4.11.0 -> 5.5.0
- React 19 support
Apollo Server Integrations for Nextjs 3.1.0 -> 4.1.0
- Next.js 16 support
Plausible 4.0.0
- React 19 support
@yudiel/react-qr-scanner 2.0.8 -> 2.5.1
- React 19 support
qrcode.react 4.0.1 -> 4.2.0
- React 19 support
react-avatar-editor 13.0.2 -> 15.1.0
- React 19 support
recharts 2.13.0 -> 2.15.4
- React 19 support
- react-is 19.2.4 override
  - can be removed after upgrade to recharts 3.x
eslint-plugin-next 14.2.15 -> 16.2.2
eslint-config-next 16.2.2

Changes

TBD

Next.js rewrites

      {
        source: '/~:sub/:slug*\\?:query*',
        destination: '/~/:slug*?:query*&sub=:sub'
      },

This rewrite rule has been removed because it's not supported by Next.js 15+
but this rule already does the same thing and is supported:

      {
        source: '/~:sub/:slug*',
        destination: '/~/:slug*?sub=:sub'
      },

Screenshots

Stacker News running on Next.js 16.2.2

Additional Context

The upgrade to Next.js 16 and React 19 required the upgrade of other core libraries, such as Apollo Client/Server.
Upgrading Apollo meant handling breaking changes to useLazyQuery, useQuery, and ApolloLink. Everything seems to be working as intended but still needs deep QA.

Safari DevTools are broken since Next.js 15 vercel/next.js#78524 if Next.js is ran without Turbopack.

Next.js now catches console.errors and show them as thrown errors in dev mode.

Apollo

Apollo breaking changes

The notifyOnNetworkStatusChange option now defaults to true. This affects React hooks that provide this option (e.g. useQuery) and ObservableQuery instances created by client.watchQuery.
This change means you might see loading states more often, especially when used with refetch or other APIs that cause fetches. If this causes issues, you can revert to the v3 behavior by setting the global default back to false.
If we use useLazyQuery to execute queries but don't read the state values returned in the result tuple, it is now recommended to use client.query directly. src
- In Apollo Client 4, useLazyQuery focuses on user interaction and more predictable data synchronization with the component. Network requests are now initiated only when the execute function is called. This makes it safe to re-render your component with new options provided to useLazyQuery without the unintended network requests. New options are used the next time the execute function is called.
- Calling the execute function of useLazyQuery during render is no longer allowed and will now throw an error, recommend instead migrating to useQuery which executes the query during render automatically.
- In-flight queries are now aborted more frequently. This occurs under two conditions:
  The component unmounts while the query is in flight
  A new query is started by calling the execute function while a previous query is in flight
  In each of these cases, the promise returned by the execute function is rejected with an AbortError. This change means it is no longer possible to run multiple queries simultaneously.
  In some cases, you may need the query to run to completion, even if a new query is started or your component unmounts. In these cases, you can call the .retain() function on the promise returned by the execute function.
useQuery got rid of onCompleted and onError callbacks
- hasNewNotes used onCompleted and has been migrated to useEffect pattern
New requirements for custom cache implementations
Custom cache implementations must now implement the fragmentMatches method, which is required for fragment matching in Apollo Client 4.

Checklist

Are your changes backward compatible? Please answer below:

tbd

On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:

7, everything seems to be working. QA done on payments, wallets, normal website interaction (post, comment, navigation), live comments, editor

For frontend changes: Tested on mobile, light and dark mode? Please answer below:
n/a

Did you introduce any new environment variables? If so, call them out explicitly here:
Yes, with Next.js 15/16 localhost is the default and only allowed dev origin. This has been modified to ensure it also always includes NEXT_PUBLIC_URL and to support additional origins, we now have a new env var:

ALLOWED_DEV_ORIGINS=

By default it's empty, which means that only localhost and NEXT_PUBLIC_URL are allowed.

Did you use AI for this? If so, how much did it assist you?

help with Apollo migration
upgrade from Next.js 15 to 16 via Next.js Devtools MCP (Claude)

Note

High Risk
High risk because it upgrades core runtime dependencies (Next.js/React/Apollo) and rewires Apollo hook/query behavior (notably useLazyQuery promise/abort semantics and removal of onCompleted), which can affect navigation, data fetching, and payments-related flows across the app.

Overview
Upgrades the frontend stack to Next.js 16/React 19 and adapts the codebase for Apollo Client 4 by switching React hooks imports to @apollo/client/react, enabling @client directive support via LocalState, and updating client config (e.g., ApolloLink.from, devtools config, and default notifyOnNetworkStatusChange: false).

Refactors multiple useLazyQuery/useQuery call sites to the new promise-based/abort-heavy behavior: moves onCompleted logic into .then(...)/useEffect, adds centralized isAbortError filtering to avoid noisy errors on aborted requests, and updates a few components (popovers, upload fee refresh, suggestions, auto-retry pay-ins) to execute queries explicitly and handle errors.

Adjusts Next.js config for v15+ compatibility and dev ergonomics: adds allowedDevOrigins derived from NEXT_PUBLIC_URL plus new ALLOWED_DEV_ORIGINS, removes an unsupported rewrite, adds transpilePackages, and silences bootstrap sass deprecation warnings; also adds a new flat eslint.config.mjs.

^{Reviewed by Cursor Bugbot for commit 36ab54b. Bugbot is set up for automated code reviews on this repo. Configure here.}

…upgrade Apollo Client/Server, other libs that didn't support React 19 - Next.js 14.2.25 -> 15.5.14 - React 18.3.1 -> 19.2.4 - GraphQL 16.9.0 -> 16.13.2 - Apollo Client 3.11.8 -> 4.1.6 - Apollo Server 4.11.0 -> 5.5.0 - Apollo Server Integrations for Nextjs 3.1.0 -> 4.1.0 - \@yudiel/react-qr-scanner 2.0.8 -> 2.5.1 - qrcode.react 4.0.1 -> 4.2.0 - react-avatar-editor 13.0.2 -> 15.1.0 - recharts 2.13.0 -> 2.15.4 - react-is 19.2.4 override - can be removed after upgrade to recharts 3.x - eslint-plugin-next 14.2.15 -> 15.5.14 + eslint-config-next 15.5.14

socket-security · 2026-04-05T14:33:26Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Vulnerability	Quality	Maintenance
next@14.2.35 ⏵ 16.2.2	⁺⁵	⁺¹⁰	^-3
eslint-config-next@16.2.2
react-avatar-editor@13.0.2 ⏵ 15.1.0	⁺¹		^-30
@next/eslint-plugin-next@14.2.35 ⏵ 16.2.2			⁺¹
recharts@2.13.0 ⏵ 2.15.4	⁺⁶		⁺¹
qrcode.react@4.0.1 ⏵ 4.2.0	⁺¹
rxjs@7.8.2
urlpattern-polyfill@10.1.0
@yudiel/react-qr-scanner@2.0.8 ⏵ 2.5.1			⁺¹	⁺³
react@18.3.1 ⏵ 19.2.4	⁺¹
bootstrap@5.3.3 ⏵ 5.3.8
react-bootstrap@2.10.5 ⏵ 2.10.10
next-plausible@3.12.2 ⏵ 4.0.0	⁺¹		⁺¹	⁺⁹
@as-integrations/next@3.1.0 ⏵ 4.1.0	⁺¹		⁺²	⁺⁶
@apollo/client@3.11.8 ⏵ 4.1.6	^-4		⁺¹⁰	^-2
react-dom@18.3.1 ⏵ 19.2.4	⁺⁸		⁺¹
@apollo/server@4.13.0 ⏵ 5.5.0	⁺¹	⁺²		⁺⁴³
graphql@16.9.0 ⏵ 16.13.2

View full report

…e boostrap sass deprecation warnings

… a server external DefinePlugin can't otherwise replace the env var internally used by next-plausible to determine if we're using the proxy or not

…get the full error where errors are manually handled

sir-opti

Did some code review on the diff, pre-testing.

Soxasora · 2026-04-06T11:21:59Z

Hi opti! All the things you found were added automatically by the Apollo Client 4 migration codemod. The @defer directive support was something I've already removed but probably got added again when I re-ran the codemod on worker and api.

Thanks you so much for checking this PR, I'll address immediately 🫡

…pollo Client where unnecessary

… getOperationAST

cursor · 2026-04-06T12:07:25Z

+    if (data && !data.hasNewNotes) {
+      clearNotifications()
+    }
+  }, [data?.hasNewNotes])


useEffect fires less often than replaced onCompleted callback

Low Severity

The useEffect with [data?.hasNewNotes] dependency only fires when the value changes, whereas the old onCompleted callback fired on every successful poll response. This means clearNotifications() is no longer called repeatedly when hasNewNotes stays false across consecutive polls. If a push notification arrives but the server-side hasNewNotes value doesn't transition (remains false), the notification won't be cleared until the next value change. The old behavior acted as a continuous cleanup sweep.

^{Reviewed by Cursor Bugbot for commit 7a6367c. Configure here.}

This seems like a good thing.

sir-opti · 2026-04-07T21:25:00Z

Seeing this, a lot:

app  | 2026-04-07T21:23:28.213872810Z `legacyBehavior` is deprecated and will be removed in a future release. A codemod is available to upgrade your components:
app  | 2026-04-07T21:23:28.213915174Z 
app  | 2026-04-07T21:23:28.213925669Z npx @next/codemod@latest new-link .
app  | 2026-04-07T21:23:28.213957697Z 
app  | 2026-04-07T21:23:28.213963226Z Learn more: https://nextjs.org/docs/app/building-your-application/upgrading/codemods#remove-a-tags-from-link-components

…ents that by default use their own

Soxasora · 2026-04-08T10:59:50Z

-          <Link href={'/' + user.name} passHref legacyBehavior>
-            <Nav.Link eventKey='bio'>bio</Nav.Link>
-          </Link>
+          <Nav.Link as={Link} href={'/' + user.name} eventKey='bio'>bio</Nav.Link>


This change has been applied to every instance of NextLink used with legacyBehavior. We're giving NextLink as the component to be used in place of the default <a> tag.

passHref then becomes useless as Nav.Link, for example, gives the href to whatever as component we indicate.

@sir-opti I was ignoring that deprecation warning to avoid touching too many things, but the solution is quite straightforward.

This is an awesome change because now my eyes only hurt 200% instead of 500% from looking at that indentation 🤣

sir-opti · 2026-04-08T21:45:16Z

Haven't found anything new between posting/deleting, editor funk, territory creation, payments/zaps/boosts, messing around with rankings and analytics - all that worked great.

I have 2 more test areas to cover on this:

Uploads (I've been pretty mad trying to get s3 to work)
Connected wallets

Also:

Debugging what's up with the websocket in my dev setup
- I think we need allowedDevOrigins: isProd ? undefined : [(new URL(process.env.PUBLIC_URL)).host], in next.config.js - unconfirmed still though
- I get an occasional page reload - didn't get that before this patch, but may be related to the websocket

Soxasora · 2026-04-08T21:49:58Z

Thank you for the QA!

I think we need allowedDevOrigins: isProd ? undefined : [(new URL(process.env.PUBLIC_URL)).host], in next.config.js - unconfirmed still though

Ah yes, we do! I've added this in the custom domains PR today d466483, but I didn't make the same reasoning for this PR (or custom hosts in general...). localhost is by default an allowed dev origin though.

I should come up with a way to satisfy both normal sndev and custom domains. I'll check it out tomorrow first thing.

Uploads (I've been pretty mad trying to get s3 to work)

I think you just need to add your host to the allowed origins in docker/s3/cors.json. Then restart (or delete + start).

…LOWED_DEV_ORIGINS env var for additional allowed origins

huumn

I'm not sure these should block merging, because afaict this would run fine in prod, but here's a few things I noticed:

Dev hits the nextjs error boundary on checkMedia if capture is not running and media is checked. I didn't check if this happens in prod, but it's annoying in dev and should probably be fixed.
One of the consequences of notifyOnNetworkStatusChange: true is that rerenders are happening when polling even if data doesn't change.
- Example: create a new comment and watch the timeSince change
- If only, this suggests I don't understand the consequences of notifyOnNetworkStatusChange: true and wonder what else might change.
components/item-popover.js, components/sub-popover.js, components/user-popover.js, components/territory-form.js, wallets/client/hooks/logger.js all log AbortError still.
Not a regression, but we pull deps from next/dist/* like NodeNextRequest which we got lucky didn't change between upgrades. Perhaps can be changed in a follow up.

Soxasora · 2026-04-14T13:32:14Z

Dev hits the nextjs error boundary on checkMedia if capture is not running and media is checked. I didn't check if this happens in prod, but it's annoying in dev and should probably be fixed.

Next.js now catches console.errors and show them as thrown errors in dev mode.

I mentioned this in this PR description, thinking that it was a new default behavior lol, but it seems like it's a bug on the pages router: vercel/next.js#75299

and media is checked

This is a behavior present on master:

  const trusted = useMemo(() => !!(srcSet || srcSetIntital) || IMGPROXY_URL_REGEXP.test(src) || MEDIA_DOMAIN_REGEXP.test(src), [srcSet, srcSetIntital, src])
  const [isImage, setIsImage] = useState((kind === 'image' || legacySrcSet?.video === false) && trusted)

If an image is uploaded, trusted will be true because at least MEDIA_DOMAIN_REGEXP.test(src) is true (being an upload), but when we convert markdown ![]() to Lexical MediaNode we always set kind: unknown triggering media checks.

We don't load the media client-side anymore to determine if it's an image or a video (or media at all), instead we always contact capture. I think we wanted to create a dedicated microservice for this.

One of the consequences of notifyOnNetworkStatusChange: true is that rerenders are happening when polling even if data doesn't change.

Just confirmed, basically it re-renders even on data.loading or data.networkStatus changes. By switching to false we're back to the original behavior, which we probably want so I'll switch back.

components/item-popover.js, components/sub-popover.js, components/user-popover.js, components/territory-form.js, wallets/client/hooks/logger.js all log AbortError still.

I'll handle AbortError in every catch for this, pretty bad that we have to do this.

Not a regression, but we pull deps from next/dist/* like NodeNextRequest which we got lucky didn't change between upgrades. Perhaps can be changed in a follow up.

Probably whatever we needed from NodeNextRequest we can get it from the public NextApiRequest for the pages router iirc.

huumn · 2026-04-14T15:36:05Z

Probably whatever we needed from NodeNextRequest we can get it from the public NextApiRequest for the pages router iirc.

It's mostly cookies parsing and in _app.js we use next/dist/client/router instead of next/router.

By switching to false we're back to the original behavior, which we probably want so I'll switch back.

I agree - that's the safest thing. Perhaps we can switch it to the default later (assuming it's worth it).

I mentioned this in this PR description, thinking that it was a new default behavior lol, but it seems like it's a bug on the pages router: vercel/next.js#75299

lol that's nasty

I'll handle AbortError in every catch for this, pretty bad that we have to do this.

It might be worth creating our own useDeferredQuery as a small wrapper around client.query, but also cool if not - borderline need for an abstraction.

Soxasora · 2026-04-14T15:45:26Z

It might be worth creating our own useDeferredQuery as a small wrapper around client.query, but also cool if not - borderline need for an abstraction.

I'm sure we won't need it if we fix the way we use useLazyQuery in some places. I'll come up with a follow-up PR refactor, for example the BaseSuggest's getSuggestions that is executed by useEffect when query !== undefined, can just be a useQuery with skip (avoiding AbortError)

…inal Apollo Client 3 behavior (don't re-render components unless data changes)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

There are 4 total unresolved issues (including 2 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 85d3e80. Configure here.}

cursor · 2026-04-14T15:52:49Z

+  return devOrigins
+}
+
+module.exports = withPlausibleProxy({ src: 'https://plausible.io/js/pa-EScEhWlTi3E-sauvdFABb.js' })({


Unrecognized src option passed to withPlausibleProxy

Medium Severity

The src option passed to withPlausibleProxy is not a recognized configuration parameter. The valid options for withPlausibleProxy are subdirectory, scriptName, and customDomain (or scriptPath/apiPath in newer versions). The src value (https://plausible.io/js/pa-EScEhWlTi3E-sauvdFABb.js) is silently ignored, meaning the proxy rewrites are configured with default paths, not the custom script URL that was clearly intended to be used.

^{Reviewed by Cursor Bugbot for commit 85d3e80. Configure here.}

export default function withPlausibleProxy(options: { /** * The site-specific script URL from your Plausible dashboard, e.g. https://plausible.io/js/pa-XXXXX.js. */ src: string; /** * The local path for the proxied script. Defaults to /js/script.js. */ scriptPath?: string; /** * The local path for the proxied API endpoint. Defaults to /api/event. */ apiPath?: string; }): (nextConfig: NextConfig) => NextConfig;

wdym??

huumn · 2026-04-14T23:50:06Z

I mentioned this in this PR description, thinking that it was a new default behavior lol, but it seems like it's a bug on the pages router: vercel/next.js#75299

I went ahead and switched mediaCheck to use console.warn. That's semantically more accurate anyway. We all tend to abuse console.error.

This is good to go now imo.

Soxasora · 2026-04-14T23:53:59Z

Thank you! You're right about console.error, will be more precise.

Soxasora and others added 2 commits April 5, 2026 16:28

Merge branch 'master' into chore/update-nextjs-16

ffb119b

Soxasora added 3 commits April 5, 2026 17:06

upgrade Bootstrap to 5.3.8; upgrade react-boostrap to 2.10.10; silenc…

e8fedc8

…e boostrap sass deprecation warnings

upgrade Next.js to 16.2.2, rename middleware.js to proxy.js

8f7e221

polyfill URLPattern and add to js-standard lint globals

fd7cb96

Soxasora changed the title ~~chore: upgrade to React 19 and Next.js 16.x~~ chore: upgrade to React 19, Next.js 16, Apollo Client 4, Apollo Server 5 Apr 5, 2026

Soxasora marked this pull request as ready for review April 5, 2026 15:52

Soxasora commented Apr 5, 2026

View reviewed changes

Comment thread api/ssrApollo.js Outdated

cursor Bot reviewed Apr 5, 2026

View reviewed changes

Comment thread components/form.js

upgrade to next-plausible 4.0.0; remove PlausibleProvider dead props

29ab41b

Soxasora marked this pull request as draft April 5, 2026 22:14

Soxasora added 2 commits April 6, 2026 01:27

fix: run withPlausibleProxy through webpack instead of treating it as…

0cf9f68

… a server external DefinePlugin can't otherwise replace the env var internally used by next-plausible to determine if we're using the proxy or not

apollo: useLazyQuery now throws AbortError, add errorPolicy 'all' to …

da82997

…get the full error where errors are manually handled

Soxasora marked this pull request as ready for review April 5, 2026 23:52

sir-opti reviewed Apr 6, 2026

View reviewed changes

Comment thread pages/items/[id]/edit.js Outdated

Comment thread components/payIn/hooks/use-pay-in-mutation.js Outdated

Comment thread worker/index.js Outdated

Comment thread worker/index.js Outdated

Soxasora added 3 commits April 6, 2026 13:26

apollo migration: remove @client and @defer directives support from A…

3813e00

…pollo Client where unnecessary

apollo migration: switch now-internal getOperationName with graphql's…

4717770

… getOperationAST

remove Apollo's execute double catch

7a6367c

cursor Bot reviewed Apr 6, 2026

View reviewed changes

Soxasora added 2 commits April 6, 2026 14:17

remove temporary nodejs nextjs 15 middleware workaround

d556244

cleanup: linting

cb5b2fd

cursor Bot reviewed Apr 6, 2026

View reviewed changes

Comment thread components/form.js Outdated

Soxasora mentioned this pull request Apr 7, 2026

custom domains: middleware and verification #2897

Open

remove legacyBehavior and passHref, use NextLink as anchor for compon…

41a0307

…ents that by default use their own

Soxasora commented Apr 8, 2026

View reviewed changes

Soxasora and others added 2 commits April 9, 2026 14:34

Merge branch 'master' into chore/update-nextjs-16

2ae1b0d

fix: allowedDevOrigins starts by default with NEXT_PUBLIC_URL, new AL…

96fd1f0

…LOWED_DEV_ORIGINS env var for additional allowed origins

cursor Bot reviewed Apr 10, 2026

View reviewed changes

Comment thread next.config.js Outdated

Soxasora added 2 commits April 10, 2026 15:20

fix: put allowedDevOrigins in the right next.config.js section

d7e6c3a

merge master, adapt changes to Apollo Client v4

5324862

cursor Bot reviewed Apr 12, 2026

View reviewed changes

Comment thread components/form.js Outdated

Merge branch 'master' into chore/update-nextjs-16

539b2a5

huumn reviewed Apr 14, 2026

View reviewed changes

huumn mentioned this pull request Apr 14, 2026

remove dead deps #2914

Merged

fix: switch back to notifyOnNetworkStatusChange false to get the orig…

85d3e80

…inal Apollo Client 3 behavior (don't re-render components unless data changes)

cursor Bot reviewed Apr 14, 2026

View reviewed changes

Soxasora added 2 commits April 14, 2026 18:00

remove dangling sub prop

1a2b129

filter AbortError from useLazyQuery executions

e5c99c6

Soxasora mentioned this pull request Apr 14, 2026

migrate lazy queries to Apollo Client 4 #2916

Open

8 tasks

change mediaCheck console log level to warn

36ab54b

huumn merged commit 764b0c5 into stackernews:master Apr 14, 2026
7 checks passed

huumn mentioned this pull request Apr 17, 2026

regression: reloading notifications by clicking on bell no longer works #2924

Closed

Uh oh!

Conversation

Soxasora commented Apr 5, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Upgrades

Changes

Screenshots

Additional Context

Checklist

Uh oh!

socket-security Bot commented Apr 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

sir-opti left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Soxasora commented Apr 6, 2026

Uh oh!

cursor Bot Apr 6, 2026

Choose a reason for hiding this comment

useEffect fires less often than replaced onCompleted callback

Uh oh!

Soxasora Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

sir-opti commented Apr 7, 2026

Uh oh!

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

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sir-opti Apr 8, 2026

Choose a reason for hiding this comment

Uh oh!

sir-opti commented Apr 8, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

Uh oh!

huumn left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Soxasora commented Apr 14, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot Apr 14, 2026

Choose a reason for hiding this comment

Unrecognized src option passed to withPlausibleProxy

Uh oh!

Soxasora Apr 14, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

huumn commented Apr 14, 2026

Uh oh!

Uh oh!

Soxasora commented Apr 14, 2026

Uh oh!

Reviewers

Assignees

Labels

Soxasora commented Apr 5, 2026 •

edited by cursor Bot

Loading

socket-security Bot commented Apr 5, 2026 •

edited

Loading

Soxasora Apr 8, 2026 •

edited

Loading

Soxasora commented Apr 8, 2026 •

edited

Loading

huumn left a comment •

edited

Loading

huumn commented Apr 14, 2026 •

edited

Loading

Soxasora commented Apr 14, 2026 •

edited

Loading

Unrecognized `src` option passed to `withPlausibleProxy`