Adjust build for Nuxt module packaging and typings#1
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "extends": "./.nuxt/tsconfig.json", | ||
| "compilerOptions": { | ||
| "target": "ES2022", | ||
| "module": "ESNext", | ||
| "moduleResolution": "Node", |
There was a problem hiding this comment.
Restore #imports path mapping for type checks
The new root tsconfig drops the previous inheritance from .nuxt/tsconfig.json and defines no paths mapping for Nuxt’s #imports, so TypeScript can no longer resolve #imports in runtime files. Running npm run test:types now fails with TS2307 for src/runtime/server/chatkit-proxy.ts because the alias is missing. Re-extending Nuxt’s generated tsconfig or adding the #imports path mapping is needed to keep the type-check scripts passing.
Useful? React with 👍 / 👎.
Summary
Testing
Codex Task