⌘K
Suheb This looks like a useful approach, especially keeping the QR generation fully client-side. Using Next.js 16 should also make it easier to keep the toolkit fast and lightweight. The focus on privacy is a nice touch since users don't need to upload their QR data to a server.
Kris Dev Thanks! That was exactly the goal. I wanted the core QR workflow to stay fully client-side so users can generate, style, and export their QR codes without sending the payload to a backend. It also keeps the architecture simple and lightweight, which fits well with the kind of utility I want QR Forge to be. Appreciate the feedback!
Tianen Pang check this one https://github.com/vercel/next.js/issues/89764#issuecomment-3928272828 for temp fix
ADALIGO The error comes from tooling mismatch not from you **Luknuts56,** just downgrade ESLint and you’re good 👍
Ryu Hi Luknuts56, This one looks like a tooling-version mismatch, not a problem with your `loading.tsx` file. Your `package.json` has: ``` "eslint": "10.0.3", "eslint-config-next": "^16.1.7" ``` and the stack trace is failing inside `eslint-plugin-react` while loading the `react/display-name` rule. There’s an open Next.js issue for this same ESLint 10 error: https://github.com/vercel/next.js/issues/89764 For now I’d pin ESLint back to v9 instead of using ESLint 10: ``` pnpm add -D eslint@^9 eslint-config-next@latest pnpm lint ``` If it still keeps ESLint 10 because of the lockfile, do a clean install: ``` rm -rf node_modules pnpm-lock.yaml pnpm install pnpm lint ``` One more thing: since you’re following a course, I’d avoid using `"latest"` for `next`, `react`, and `react-dom`. The tutorial may have been written for a slightly older version, while `latest` can pull in newer Next/React/ESLint behavior than the lesson expects. So the short version is: downgrade/pin ESLint to v9, reinstall, and rerun `pnpm lint`.
Codex 5427 Yeah I know
ADALIGO 😄 Haha... imagine creating a brand new account just to write: "Yeah I know." But anyway... let me tell you something maybe you *don't* know yet: Even if someone knows a lot, nobody knows everything. Real builders stay humble. Real engineers keep learning. 🚀 Knowledge is not about acting bigger than others. It's about helping, encouraging, building, and evolving together. So whether you're senior, junior, beginner, or expert: keep learning 📚 keep building ⚡ keep improving 🧠 Because technology moves fast... and the moment someone thinks they know everything, they already stopped growing. Still building. Still learning. Still evolving. 🌍🔥 ***Real knowledge is not saying:*** ***"Yeah I know."*** ***Real knowledge is understanding*** https://community.vercel.com/t/introductions-2026/39946?u=nfdcopilot-5305 SAY HI TO VERCEL COMMUNITY
Benjamin Woodruff This is lacking the context to know what your issue is. You’d need to share the contents of that logfile, or click on the link to create a GitHub discussion. But, since you’re on Windows, I’m guessing this might’ve been https://github.com/vercel/next.js/discussions/86668, which is fixed in 16.1.1. Sorry about that!
Shubham kahar Solved This error is caused by symlink permissions. Settings > Update & Security > For developers > Turn on Developer Mode Worked for me.
