i_use_arch_btw Comments

i_use_arch_btw

•Created by i_use_arch_btw on 3/25/2025 in #help

Workspace-aware path imports

This, tied with inability to produce NPM tarballs for a JSR package, makes it very difficult to test changes / prototype new features to the workspace A locally, as an "external" user of the packages =(

4 replies

DDeno

•Created by i_use_arch_btw on 3/25/2025 in #help

Workspace-aware path imports

This does not address my issue, unfortunately. I technically have 2 different workspaces. And I want to import package(s) from workspace A in workspace B, treating workspace A as a "black box". As an experiment, I tried to define package of workspace A as a "member" in workspace B, and I got an error:

{
  "workspace": {
    "members": ["../workspace-a/packages/core"]
  }
}

{
  "workspace": {
    "members": ["../workspace-a/packages/core"]
  }
}

error: Workspace member must be nested in a directory under the workspace.
  Member: file:///home/quacumque/Projects/workspace-a/packages/core/
  Workspace: file:///home/quacumque/Projects/workspace-b/

error: Workspace member must be nested in a directory under the workspace.
  Member: file:///home/quacumque/Projects/workspace-a/packages/core/
  Workspace: file:///home/quacumque/Projects/workspace-b/

4 replies