How to prevent specific workspace members from being published to JSR?
📰JSR✅Solved
Hi everyone!
I'm currently working on a Deno monorepo using the workspaces feature. I have a question regarding publishing to JSR.
In my monorepo, I have several packages. Some of them are meant to be internal-only and should never be published to JSR. However, other packages in the workspace are public and need to be published.
Here's the catch:
1. I cannot simply remove the
2. In the npm ecosystem, I would use
Is there an equivalent field or a recommended way in Deno/JSR to mark a workspace member as “private” so that
If such a feature doesn't exist yet, what is the best practice to manage this? Should I manually manage the publish command for each package in CI, or is there a way to exclude specific members in the root deno.json?
Thanks in advance!
I'm currently working on a Deno monorepo using the workspaces feature. I have a question regarding publishing to JSR.
In my monorepo, I have several packages. Some of them are meant to be internal-only and should never be published to JSR. However, other packages in the workspace are public and need to be published.
Here's the catch:
1. I cannot simply remove the
name2. In the npm ecosystem, I would use
"private": trueIs there an equivalent field or a recommended way in Deno/JSR to mark a workspace member as “private” so that
deno publishIf such a feature doesn't exist yet, what is the best practice to manage this? Should I manually manage the publish command for each package in CI, or is there a way to exclude specific members in the root deno.json?
Thanks in advance!
