fix: compile console plugin.ts to JS for Node.js runtime compatibility

[Copilot]

@object-ui/console ships "main": "./plugin.ts" — a raw TypeScript entry point. Downstream projects (e.g. hotcrm on Vercel) that keep node_modules external during bundling hit ERR_MODULE_NOT_FOUND at runtime because Node.js cannot execute .ts files natively.

Changes

• tsconfig.plugin.json — New tsconfig that compiles plugin.ts → plugin.js + plugin.d.ts with nodenext module resolution for Node.js runtime compatibility
• package.json — Entry points now reference compiled output:
  • main → ./plugin.js, types → ./plugin.d.ts
  • exports updated with proper types/import/default conditions
  • build:plugin script added, chained into build and build:vercel
  • plugin.js and plugin.d.ts added to files
• .gitignore — Excludes generated plugin.js / plugin.d.ts

Before/After

// Before — Node.js fails at runtime
{ "main": "./plugin.ts" }

// After — works in any Node.js environment
{ "main": "./plugin.js", "types": "./plugin.d.ts" }

plugin.ts source is still included in the published package for reference. Monorepo-internal relative imports (../../apps/console/plugin) continue to resolve to the .ts source via TypeScript.

Original prompt

fix 下游hotcrm项目集成console后报错， Investigate the ERR_MODULE_NOT_FOUND error for @object-ui/console/plugin.ts
Root cause: @object-ui/console npm package has "main": "./plugin.ts" (TypeScript entry point). Vercel's @vercel/node keeps node_modules external during bundling, so at runtime Node.js tries to import plugin.ts directly — but Node.js cannot execute TypeScript files natively.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectui	Error		Feb 14, 2026 0:40am
objectui-demo	Error		Feb 14, 2026 0:40am
objectui-storybook	Error		Feb 14, 2026 0:40am

[Copilot]

Pull request overview

This PR fixes a runtime compatibility issue where @object-ui/console was shipping raw TypeScript source (plugin.ts) as its entry point, causing ERR_MODULE_NOT_FOUND errors in production environments like Vercel that keep node_modules external during bundling. Node.js cannot execute TypeScript files natively, so the plugin must be compiled to JavaScript before publication.

Changes:

• Added dedicated TypeScript compilation configuration for the plugin entry point
• Updated package.json to reference compiled JavaScript output while preserving TypeScript source for reference
• Configured build pipeline to generate plugin.js and plugin.d.ts during the build process

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
apps/console/tsconfig.plugin.json	New TypeScript configuration for compiling plugin.ts to Node.js-compatible JavaScript with nodenext module resolution
apps/console/package.json	Updated entry points to reference compiled plugin.js, added build:plugin script, included compiled outputs in published files
apps/console/.gitignore	Excludes generated plugin.js and plugin.d.ts from version control

[Copilot]

The tsconfig is missing the outDir compiler option. Without it, TypeScript will emit the compiled plugin.js and plugin.d.ts files in the same directory as the source file (the root of apps/console/), which is the desired behavior based on the .gitignore entries. However, it's a best practice to explicitly specify outDir: "." for clarity, and to ensure the configuration is self-documenting. Consider adding "outDir": "." to the compilerOptions.

Suggested change

	"esModuleInterop": true
	"esModuleInterop": true,
	"outDir": "."