supermemory icon indicating copy to clipboard operation
supermemory copied to clipboard

Upgrade supermemory consumer app to Next.js 16

Open MaheshtheDev opened this issue 3 months ago • 9 comments

We're looking to upgrade the Supermemory consumer app from its current Next.js version 15.3.0 to Next.js 16.

Tasks/Requirements:

  • [ ] Make sure you test the web application before submitting the PR.
  • [ ] Build locally to check if all requirements are met.

MaheshtheDev avatar Nov 03 '25 03:11 MaheshtheDev

ENG-363

linear[bot] avatar Nov 03 '25 03:11 linear[bot]

i would love to work on this, can you assign it to me @MaheshtheDev

PhantomInTheWire avatar Nov 03 '25 04:11 PhantomInTheWire

@PhantomInTheWire assigned 👍

MaheshtheDev avatar Nov 03 '25 04:11 MaheshtheDev

Hey @MaheshtheDev , I’ve been working on this and got pretty far, but I noticed that running bun run build on the main branch seems to be broken. It looks like the issue is related to the @repo alias. I can fix it locally by adjusting some configs, but since the app is deployed to Cloudflare automatically on every commit via CI, I’m assuming I might be missing something. Could you take a look and help me out?

PhantomInTheWire avatar Nov 03 '25 09:11 PhantomInTheWire

Hey guys, just a quick question how you guys have planned to implement it?

is it basic or a extensive migration like converting pages to PPR (cache components) wherever required or just middleware -> proxy???

AntonVishal avatar Nov 03 '25 13:11 AntonVishal

hey @AntonVishal right now im fixing mostly breaking changes and some simple QOL stuff like turbopackFileSystemCacheForDev. other stuff would have be a part of subsequent prs(if needed), im trying to keep the pr clean and well scoped

PhantomInTheWire avatar Nov 03 '25 14:11 PhantomInTheWire

Ah I see, Agree even I tried turbopackFileSystemCacheForDev in another project the boost was noticeable.

AntonVishal avatar Nov 03 '25 16:11 AntonVishal

Hey @MaheshtheDev , I’ve been working on this and got pretty far, but I noticed that running bun run build on the main branch seems to be broken. It looks like the issue is related to the @repo alias. I can fix it locally by adjusting some configs, but since the app is deployed to Cloudflare automatically on every commit via CI, I’m assuming I might be missing something. Could you take a look and help me out?

@PhantomInTheWire , On PR creation, cloudflare will do build test and on commits as well

MaheshtheDev avatar Nov 03 '25 18:11 MaheshtheDev

@MaheshtheDev it seems it will require approval, plus its fine if cloudflare does build and test on its own, what surprises me is that i can't get it to build locally without some tsconfig changes, minimal reproduction steps would be

  1. clone the repo
  2. bun install
  3. bun run build

this is on macos 26

PhantomInTheWire avatar Nov 04 '25 02:11 PhantomInTheWire