Wow I just updated from 3.2.0 and it's another 130Mb less, awesome job guys!
![]() |
VOOZH | about |
| Git Clone URL: | https://aur.archlinux.org/seerr.git (read-only, click to copy) |
|---|---|
| Package Base: | seerr |
| Description: | Request management and media discovery tool for the Plex ecosystem |
| Upstream URL: | https://github.com/seerr-team/seerr |
| Licenses: | MIT |
| Submitter: | fryfrog |
| Maintainer: | fryfrog (txtsd, mmozeiko) |
| Last Packager: | mmozeiko |
| Votes: | 8 |
| Popularity: | 0.66 |
| First Submitted: | 2025-10-10 17:26 (UTC) |
| Last Updated: | 2026-06-03 04:23 (UTC) |
Wow I just updated from 3.2.0 and it's another 130Mb less, awesome job guys!
For me aur build produces usr/lib/seerr/.next/node_modules/@tanem/react-nprogress-866109adae1535af folder with package.json file & dist folder. And that gets packaged into .pkg file. If I look inside installed /usr/lib/seerr/.next/server/chunks/ssr/[root-of-the-server]__0be1-xm._.js file - that contains require("@tanem/react-nprogress-866109adae1535af") which matches installed folder name on disk - /usr/lib/seerr/.next/node_modules/@tanem/react-nprogress-866109adae1535af. So not sure what is going on here, I do not need to strip out these hashes at all.
It looks like the root cause is that Turbopack bakes path-derived hashes into SSR bundle require() calls at build time. The bundle ends up with literals like require("@tanem/react-nprogress-013bd7944d3bca60") where the hex suffix is hashed from the package's resolved path in the build directory. At runtime, Node tries to find a package by that name, fails, and causes a 500 to be thrown. This happens regardless of which pruning approach is used.
The existing sed in package() fixed plaintext path references but can't touch these hashes. One more pass after that does the trick:
find "${pkgdir}/usr/lib/seerr/.next/server" -type f -name "*.js" -exec sed -i -E 's/-[0-9a-f]{16}(["\/])/\1/g' {} +
This rewrites @tanem/react-nprogress-013bd7944d3bca60 -> @tanem/react-nprogress, next-6d7da243f4748cff/dist/client/router.js -> next/dist/client/router.js, etc. across all server chunks.
I think it is an overkill to do all the cleanup for those tiny files. The initial cleanup I did in https://aur.archlinux.org/cgit/aur.git/commit/?h=seerr&id=3f463062c68704c830fe982a9fddfd0722ce5ae3 already removes majority of big files (~57% savings, from 1011MB to 428MB). Those files are definitely not needed and is pretty safe. Whatever was added later to clean up those tiny files really gives less than 2% of extra space (1011MB to 414MB), imho it is not worth it.
That said, latest PKGBUILD does build & run fine for me. Are you sure this is not some issue with how your package manager builds package? Have you tried building in clean space with regular makepkg command?
That's the annoying thing about that sort of pruning we did, it's brittle. But if you remove that it's probably bloating again. Maybe someone has a contact with upstream and they're willing to trim themselves
@orixio I was able to fix that by removing the pnpm prune --prod --ignore-scripts line and the # Remove unneeded files section from the PKGBUILD.
Seerr is starting but the webui does not work.
Error: Failed to load external module @tanem/react-nprogress-013bd7944d3bca60: Error: Cannot find module '@tanem/react-nprogress-013bd7944d3bca60'
Require stack:
- /usr/lib/seerr/.next/server/chunks/ssr/[root-of-the-server]__0ghdpmo._.js
- /usr/lib/seerr/.next/server/chunks/ssr/[turbopack]_runtime.js
- /usr/lib/seerr/.next/server/pages/_document.js
- /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/require.js
- /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/next-server.js
- /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/next.js
- /usr/lib/seerr/dist/index.js
at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:624:15)
at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__0ghdpmo._.js:10:87502)
at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:853:9)
at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:877:12)
at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:281:20)
at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__0ghdpmo._.js:10:87645)
at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:853:9)
at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:877:12)
at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:281:20)
at <unknown> (.next/server/chunks/ssr/[root-of-the-server]__0ghdpmo._.js:10:102849)
This should be now fixed, works with latest nodejs for me.
Seerr crash on start complaining of a missing next-test module. I had to update to nodejs 22 to get that far. 24 is the same. Haven't tried 26.
at Object.<anonymous> (/usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/config-s>
at require (node:internal/modules/helpers:152:16)
at mod.require (/usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/require-hook.js>
at Module.<anonymous> (node:internal/modules/cjs/loader:1556:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
at Module._load (node:internal/modules/cjs/loader:1242:25)
at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1071:22)
at defaultResolveImpl (node:internal/modules/cjs/loader:1066:19)
at /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/require-hook.js:68:36
at Module.<anonymous> (node:internal/modules/cjs/loader:1456:15)
- /usr/lib/seerr/dist/index.js
- /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/next.js
- /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/lib/start-server.js
- /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/lib/app-info-log.js
- /usr/lib/seerr/node_modules/.pnpm/next@16.2.6_@babel+core@7.29.0_babel-plugin-macros@3.1.0_react-dom@19.2.6_react@19.2.6__react@19.2.6/node_modules/next/dist/server/config-schema.js
Require stack:
2026-06-02T18:43:29.559Z [error]: Error: Cannot find module '../cli/next-test'
2026-06-02T18:43:29.513Z [info]: Starting Seerr version 3.3.0
2026-06-02T18:43:29.397Z [info]: Commit Tag: 3.3.0
Edit: Thank you for the quick fix.