anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[JS SDK] export field in package.json breaks Vite resolution #1807

New Issue
Closed
opened 2026-02-16 17:32:42 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 17:32:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @wan-kong on GitHub (Sep 24, 2025).

Originally assigned to: @thdxr on GitHub.

When using the JS SDK with Vite, I encountered the following error:

✘ [ERROR] Failed to resolve entry for package "@opencode-ai/sdk".
The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-scan]

After checking the package.json, I noticed it includes a custom export field named development:

"exports": {
   ".": {
      "development": "./src/index.ts",
      "import": "./dist/index.js",
      "types": "./dist/index.d.ts"
    },
}

However, according to the package.json schema, there is no standard development condition.
This seems to cause Vite’s dependency resolver to fail.

Questions
• Why is the development field present here?
• Is it an intentional extension, or a mistake?
• Should this be replaced with something like "default" or another officially supported condition?

Originally created by @wan-kong on GitHub (Sep 24, 2025). Originally assigned to: @thdxr on GitHub. When using the JS SDK with Vite, I encountered the following error: ✘ [ERROR] Failed to resolve entry for package "@opencode-ai/sdk". The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-scan] After checking the package.json, I noticed it includes a custom export field named development: ``` "exports": { ".": { "development": "./src/index.ts", "import": "./dist/index.js", "types": "./dist/index.d.ts" }, } ``` However, according to the [package.json schema](https://json.schemastore.org/package.json), there is no standard development condition. This seems to cause Vite’s dependency resolver to fail. Questions • Why is the development field present here? • Is it an intentional extension, or a mistake? • Should this be replaced with something like "default" or another officially supported condition?
yindo closed this issue 2026-02-16 17:32:42 -05:00
yindo commented 2026-02-16 17:32:42 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 24, 2025):

hmm we will fix this

@rekram1-node commented on GitHub (Sep 24, 2025): hmm we will fix this
yindo commented 2026-02-16 17:32:42 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1807
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?