V1 Beta Bug? Fresh Quickstart Fails — ./a2a/store Not Exported by @mastra/server
Message
Hey! I think there’s a packaging issue in the V1 beta.
A fresh quickstart using bun create mastra@beta fails immediately when running bun run dev / mastra dev:
Error [PLUGIN_ERROR]: Package subpath './a2a/store' is not defined by "exports" in @mastra/server/package.json
Repro steps:
mkdir test && cd test
bun create mastra@beta
cd <project>
bun install
bun run dev
Version mismatch from npm ls:
@mastra/core@1.0.0-beta.5
@mastra/deployer@1.0.0-beta.5
@mastra/server@1.0.3 <-- expects @mastra/core "^0.8.3"
Looks like the deployer is expecting a newer @mastra/server with the a2a/store export, but npm pulls an older server that depends on core 0.8.x.
Anyone else seeing this? And is there a correct server version to pin for V1 beta?
Thanks! 🙏
10 Replies
📝 Created GitHub issue: https://github.com/mastra-ai/mastra/issues/10676
🔍 If you're experiencing an error, please provide a minimal reproducible example whenever possible to help us resolve it quickly.
🙏 Thank you for helping us improve Mastra!
Hi @dimitrios are you using npm?
We have been seeing an issue where NPM is resolving a deprecated package for @mastra/server
Seems pnpm does resolve this properly, but yarn/npm are pulling in the old deprecated version from a bad publish MONTHS ago
The server can be resolved to the same version as mastra/core
https://www.npmjs.com/package/@mastra/server/v/1.0.0-beta.5
i have a feeling our next release will remove this issue and npm wont resolve that version in semver
@Abhi Aiyer I'm using bun and noticing the same issue
I think they’re resolving from the same place bun/npm.
We will push a fix for this somehow
Specifying overrides and pinning the version doesn't help as well
Put @mastra/server in dependencies and ditch the overrides
What node version are you on?
I can't repro it on Node v22 though strange
Using bun 1.3.3
Hey @Gautham & @dimitrios ! Sorry to hear you're running into this issue. Could you try adding the package below:
Then delete your
node_modules folder and your bun.lock file and finally do a bun install. This should clear the error temporarily until we ship a better fix 😉Yup, deleting the bun.lock and node_modules and a fresh install worked
Woo hoo!