fix(module): register _refreshHandler auto-import without .ts extension

[kboshold]

🔗 Linked issue

Closes #1093

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The module registered the _refreshHandler auto-import using the generated template's .dst, which still carries a .ts extension. Nuxt's auto-import codegen normalizes that specifier inconsistently across commands: nuxt dev/nuxt prepare keep the .ts, while nuxt typecheck drops it. Because imports.d.ts is a global declaration, that flip rewrites it on every command switch and invalidates the vue-tsc incremental cache, so the next type check runs cold.

This strips the extension with TS_ENDS_RE, the same treatment the module already applies to the custom-handler path a few lines up. With it gone, nuxt dev, nuxt prepare, and nuxt typecheck all emit the identical import('../refreshHandler') line, so the global declaration stops changing and the cache survives. Resolution is unaffected: nuxt typecheck was already emitting and type-checking that exact extensionless form.

On a large Nuxt 4 app, a controlled before/after benchmark showed the dev-to-typecheck path drop from about 150s (cold) to about 21s (warm), roughly 7x. Full details and the benchmark log are in #1093.

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@sidebase/nuxt-auth@1094

commit: ed4aca9