Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@elizaos/[email protected] has incorrect workspace dependency reference #2721

Closed
genialtechie opened this issue Jan 23, 2025 · 7 comments
Closed
Labels
bug Something isn't working

Comments

@genialtechie
Copy link

genialtechie commented Jan 23, 2025

Describe the bug
Installation fails when using pnpm due to an incorrect workspace dependency reference in @elizaos/[email protected]. The package incorrectly references @elizaos/core using a workspace protocol (workspace:*) instead of a proper version number.

To Reproduce

  1. Create a new project
  2. Add the following to package.json:
{
  "dependencies": {
    "@elizaos/adapter-supabase": "0.1.8",
    "@elizaos/client-discord": "0.1.8",
    "@elizaos/client-direct": "0.1.8",
    "@elizaos/core": "0.1.8",
    "@elizaos/plugin-bootstrap": "0.1.8",
    "@elizaos/plugin-node": "0.1.8"
  }
}
  1. Run pnpm install
  2. Observe the error:
ERR_PNPM_WORKSPACE_PKG_NOT_FOUND  In : "@elizaos/core@workspace:*" is in the dependencies but no package named "@elizaos/core" is present in the workspace

This error happened while installing the dependencies of @elizaos/[email protected]
 at @elizaos/[email protected]

Expected behavior
The package should install successfully using pnpm. The @elizaos/plugin-tee-log package should reference @elizaos/core using a proper version number (e.g. "0.1.8") instead of using workspace protocol.

Additional context

  • Error occurs in @elizaos/[email protected] which is a dependency of @elizaos/[email protected]
  • Attempted workarounds:
    • Using different package managers (npm, yarn, pnpm)
    • Configuring .npmrc with various workspace settings
    • Trying to disable workspace protocol resolution
  • Using yarn instead of pnpm appears to work around the issue
  • Environment:
    • OS: macOS 21.6.0
    • Package Manager: pnpm
    • Node.js version: [22.13.1]
@genialtechie genialtechie added the bug Something isn't working label Jan 23, 2025
Copy link
Contributor

Hello @genialtechie! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor!

@mirageN1349
Copy link

I used yarn and it solved the problem. But this is a temporary solution

  • rm -rf node_modules
  • yarn

@ryanleecode
Copy link
Contributor

@shakkernerd this needs an immediate hotfix

@Avantle
Copy link

Avantle commented Jan 27, 2025

Any updates on it? @shakkernerd

@mirageN1349
Copy link

@shakkernerd Maybe i may fix it and create PR?

@abuntin
Copy link

abuntin commented Jan 28, 2025

@shakkernerd Maybe i may fix it and create PR?

nah needs an owner that can push to npm to fix it, it would just be changing these lines to reflect the published packages on npm

 {
    "name": "@elizaos/plugin-tee-log",
    "version": "0.1.8+build.1",
    "main": "dist/index.js",
    "type": "module",
    "types": "dist/index.d.ts",
    "dependencies": {
        "@elizaos/core": "workspace:*", //< ------- this line
        "@elizaos/plugin-tee": "workspace:*", //<------- and this
        "@elizaos/plugin-sgx": "workspace:*", // <------- and this
        "better-sqlite3": "11.6.0",
        "elliptic": "6.6.1"
    },
    "devDependencies": {
        "@types/node": "^20.0.0",
        "tsup": "8.3.5"
    },
    "scripts": {
        "build": "tsup --format esm --dts",
        "dev": "tsup --format esm --dts --watch",
        "lint": "eslint --fix  --cache ."
    }
}

@shakkernerd
Copy link
Member

Alright, I just published new changes to the npm registry and all these errors should be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants