Do all workspace: dependencies of a published package always need to be published too?

[jschuur]

I have a pnpm monorepo with an app that has an internal package as a workspace:* dependency (sample repo):

  "dependencies": {
    "@joostschuur/hello": "workspace:*"
  }

If I publish the app to an npm registry, do I always need to publish each of my local workspace: dependencies as a separate package too?

Of course, without a valid package name resolution, another package manager wouldn't know what to do with the @joostschuur/hello workspace dependency. I understand why this generates an error:

❯ npm -g i @joostschuur/jshello
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@joostschuur%2fhello - Not found
npm ERR! 404
npm ERR! 404  '@joostschuur/[email protected]' is not in this registry.

pnpm also helps with versioning when publishing, which is good.

After I also published @joostschuur/hello, I could successfully do an npm install of the sample jshello app that used it.

My question is really whether there is some other approach I'm missing here. No way to explicitly include these workspace dependencies in my published files and then have local references to them?

Even if I bundled everything to a single file, wouldn't an npm install process still see dependencies listed and then try and install them and run into the same error?

[HuakunShen]

I have the same question, have you solved it @jschuur ?
The only solution I can think of is remove the dependency from package.json before publish.