Skip to content

Conversation

@eniewold
Copy link
Owner

Summary

  • add a Nuxt-targeted build script and configuration to create the module package
  • generate a single bundled type definition via a post-build script
  • align TypeScript configs with the module build process

Testing

  • npm run build

Codex Task

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment on lines 1 to +5
{
"extends": "./.nuxt/tsconfig.json",
"compilerOptions": {
"target": "ES2022",
"module": "ESNext",
"moduleResolution": "Node",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants