not getting any autocompletion or suggestion for nuqs

[ManabBala]

I am trying to use nuqs in my existing next project on vscode. But i am getting a weird issue of not getting any code or imort suggestion for nuqs. I have copy pasted the import statements and code sniptet and typescirpt and eslint is happy and my nuqs implementation is working.

The interesting thing is it is the suggestion and autocompletion is working on a new bare next app.

So can someone please direct me to a direction on how to debug this issue?

what i have already done:

• creaning npm caches,
• .next and node_modules folder rebuilding
• restarting both vscode, ts-server and linux pc

This is my package.json:

{
  "name": "neet-and-clear",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev --turbopack",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "prisma": {
    "seed": "tsx prisma/seed.ts"
  },
  "dependencies": {
    "@clerk/nextjs": "^6.12.9",
    "@hookform/resolvers": "^4.1.3",
    "@prisma/client": "^6.5.0",
    "@prisma/extension-accelerate": "^1.3.0",
    "@radix-ui/react-dialog": "^1.1.6",
    "@radix-ui/react-label": "^2.1.2",
    "@radix-ui/react-navigation-menu": "^1.2.5",
    "@radix-ui/react-radio-group": "^1.2.3",
    "@radix-ui/react-select": "^2.1.6",
    "@radix-ui/react-separator": "^1.1.2",
    "@radix-ui/react-slot": "^1.1.2",
    "class-variance-authority": "^0.7.1",
    "clsx": "^2.1.1",
    "date-fns": "^4.1.0",
    "lucide-react": "^0.483.0",
    "next": "^15.2.5",
    "nuqs": "^2.4.1",
    "react": "^19.0.0",
    "react-dom": "^19.0.0",
    "react-hook-form": "^7.54.2",
    "react-icons": "^5.5.0",
    "svix": "^1.62.0",
    "tailwind-merge": "^3.0.2",
    "tw-animate-css": "^1.2.4",
    "zod": "^3.24.2"
  },
  "devDependencies": {
    "@eslint/eslintrc": "^3",
    "@tailwindcss/postcss": "^4",
    "@trivago/prettier-plugin-sort-imports": "^5.2.2",
    "@types/node": "^20",
    "@types/react": "^19",
    "@types/react-dom": "^19",
    "eslint": "^9",
    "eslint-config-next": "15.2.3",
    "prisma": "^6.5.0",
    "tailwindcss": "^4",
    "tsx": "^4.19.3",
    "typescript": "^5"
  }
}

[franky47]

Thanks, I have noticed a similar behaviour, and it seems to be related to the project size: after a certain scale, VSCode just stops resolving nuqs for intellisense..

It could be related to the bundling issues we have in #708, and possibly the fact that some (most) exports are duplicated between nuqs and nuqs/server.

I'm not sure how to debug intellisense itself, to see what we can change to get it to work.