Skip to content

Comments

feat(station): exports specification.#1065

Open
samchon wants to merge 1 commit intomainfrom
feat/dto-validate-db-schema-property
Open

feat(station): exports specification.#1065
samchon wants to merge 1 commit intomainfrom
feat/dto-validate-db-schema-property

Conversation

@samchon
Copy link
Member

@samchon samchon commented Feb 10, 2026

Not agent package yet, but someday soon.

@samchon samchon requested a review from sunrabbit123 February 10, 2026 07:14
@samchon samchon self-assigned this Feb 10, 2026
@samchon samchon added the enhancement New feature or request label Feb 10, 2026
@samchon samchon marked this pull request as ready for review February 10, 2026 08:40
Copilot AI review requested due to automatic review settings February 10, 2026 08:40
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds exports fields to several @autobe/* packages to define package entrypoints (and allow ./package.json access), with the apparent goal of improving packaging/consumption behavior as these packages are published.

Changes:

  • Add top-level exports mapping . to ./src/index.ts (and allow ./package.json) in multiple packages.
  • Add/extend publishConfig.exports to map published entrypoints to ./lib/* outputs.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file
File Description
packages/utils/package.json Adds exports and moves/extends publishConfig with a lib-based exports map
packages/rpc/package.json Adds exports and moves/extends publishConfig with a lib-based exports map
packages/interface/package.json Adds exports and moves/extends publishConfig with a lib-based exports map
packages/filesystem/package.json Adds top-level exports and extends publishConfig with a lib-based exports map
packages/compiler/package.json Adds top-level exports and extends publishConfig with a lib-based exports map
packages/benchmark/package.json Adds exports and moves/extends publishConfig with a lib-based exports map

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 5 to +7
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

The new top-level exports points to ./src/index.ts. Because exports takes precedence over main, consumers (including Node at runtime) will resolve to a .ts file, even though the package build outputs lib/*.js. If this package is meant to be consumable after prepack/publish, the top-level exports should point at ./lib/index.js (and types to ./lib/index.d.ts) instead of relying on publishConfig.exports (which package resolvers don’t use).

Suggested change
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"exports": {
".": {
"types": "./lib/index.d.ts",
"default": "./lib/index.js"
},

Copilot uses AI. Check for mistakes.
Comment on lines 5 to +7
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

The new top-level exports points to ./src/index.ts. Because exports takes precedence over main, consumers (including Node at runtime) will resolve to a .ts file, even though the package build outputs lib/*.js. If this package is meant to be consumable after prepack/publish, the top-level exports should point at ./lib/index.js (and types to ./lib/index.d.ts) instead of relying on publishConfig.exports (which package resolvers don’t use).

Suggested change
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"exports": {
".": {
"types": "./lib/index.d.ts",
"default": "./lib/index.js"
},

Copilot uses AI. Check for mistakes.
Comment on lines 5 to +7
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

The new top-level exports points to ./src/index.ts. Because exports takes precedence over main, consumers (including Node at runtime) will resolve to a .ts file, even though the package build outputs lib/*.js. If this package is meant to be consumable after prepack/publish, the top-level exports should point at ./lib/index.js (and types to ./lib/index.d.ts) instead of relying on publishConfig.exports (which package resolvers don’t use).

Suggested change
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"exports": {
".": "./lib/index.js",

Copilot uses AI. Check for mistakes.
Comment on lines 5 to +7
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

The new top-level exports points to ./src/index.ts. Because exports takes precedence over main, consumers (including Node at runtime) will resolve to a .ts file, even though the package build outputs lib/*.js. If this package is meant to be consumable after prepack/publish, the top-level exports should point at ./lib/index.js (and types to ./lib/index.d.ts) instead of relying on publishConfig.exports (which package resolvers don’t use).

Suggested change
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"exports": {
".": {
"types": "./lib/index.d.ts",
"default": "./lib/index.js"
},

Copilot uses AI. Check for mistakes.
Comment on lines 5 to +7
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

The new top-level exports points to ./src/index.ts. Because exports takes precedence over main, consumers (including Node at runtime) will resolve to a .ts file, even though the package build outputs lib/*.js. If this package is meant to be consumable after prepack/publish, the top-level exports should point at ./lib/index.js (and types to ./lib/index.d.ts) instead of relying on publishConfig.exports (which package resolvers don’t use).

Suggested change
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"exports": {
".": {
"types": "./lib/index.d.ts",
"default": "./lib/index.js"
},

Copilot uses AI. Check for mistakes.
Comment on lines 5 to +7
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

The new top-level exports points to ./src/index.ts. Because exports takes precedence over main, consumers (including Node at runtime) will resolve to a .ts file, even though the package build outputs lib/*.js. If this package is meant to be consumable after prepack/publish, the top-level exports should point at ./lib/index.js (and types to ./lib/index.d.ts) instead of relying on publishConfig.exports (which package resolvers don’t use).

Suggested change
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"exports": {
".": {
"types": "./lib/index.d.ts",
"default": "./lib/index.js"
},

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant