Skip to content
Discussion options

You must be logged in to vote

The deepest ESM cause identifies an out-of-tree plugin compatibility failure, not a failed core rebuild. Both failing rows load from ~/.dsh/profiles/web/node_modules/@a1soyo0/dsh-agy/... and import a runtime value named CallId.\n\nIn rc.2, @deepseek-ai/dsh-llm exported the CallId branded constructor. In alpha.1 (cd5ef814), that runtime brand is named ToolCallId; CallId is no longer exported. A plugin bundle built against the rc.2 value surface cannot boot under the alpha.1 core closure just because pnpm installed it successfully.\n\nChoose one compatible pair:\n\n- If alpha.1 is required, update @a1soyo0/dsh-agy to a release that explicitly supports alpha.1 / ToolCallId.\n- If this plugin…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by JasonYadi
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants