Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Lerna/NX not supported with Deno

Open
#425 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
deno, typescript

Research direction

Run deno run -A build from the repository root to reproduce the Nx plugin-worker loading error. Inspect the root build script and the Lerna/Nx configuration for assumptions about runtime or module loading. Done means the root build completes successfully under Deno without breaking the existing npm-script workflow.

Written by the indexing model from the issue text.

Description

Describe the bug

While running all the tests on the Bun+Deno realized that Lerna+NX is not supported with Deno and causing error.

❯ deno run -A build
Task build lerna run build
lerna notice cli v8.1.9
error: Unable to load /ssz/node_modules/.deno/[email protected]/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker

Caused by:
    No such file or directory (os error 2)
error: Unable to load /ssz/node_modules/.deno/[email protected]/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker

Caused by:
    No such file or directory (os error 2)
error: Unable to load /ssz/node_modules/.deno/[email protected]/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker

Caused by:
    No such file or directory (os error 2)

Expected behavior

There should not be any issue running npm scripts with different runtimes.

Steps to Reproduce

  • Build the code with deno using deno run -A build on the root of the repo.
Dominant language
TypeScript
Stars
62
Forks
27
Avg merge
19h 2m
Merged PRs (30d)
6

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ChainSafe/ssz

All issues in ChainSafe/ssz

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.