You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we publish dev builds to npm under the same code-server name and tag it with a PR like code-server@4569. Instead, we should publish dev builds to a separate npm namespace: @coder/code-server-pr.
Basically, we need to add a line there that replaces "name": "code-server" with "name": "@coder/code-server-pr". That should be it. We shouldn't have to add a new NPM_TOKEN since they're not scoped to packages.
Why do you want this feature?
As @jawnsy brought up, this is cluttering the tags under the code-server package and makes it look ugly but also makes it hard for users to see actual versions.
Are there any workarounds to get this functionality today?
The current workaround is to just leave it as is.
Are you interested in submitting a PR for this?
Yes! But also open to mentor others who might be interested in doing this :)
The text was updated successfully, but these errors were encountered:
What is your suggestion?
Currently, we publish dev builds to npm under the same code-server name and tag it with a PR like
code-server@4569
. Instead, we should publish dev builds to a separate npm namespace:@coder/code-server-pr
.How to do this?
We'll need to modify this logic
https://github.com/coder/code-server/blob/main/ci/steps/publish-npm.sh#L111-L118
Basically, we need to add a line there that replaces
"name": "code-server"
with"name": "@coder/code-server-pr"
. That should be it. We shouldn't have to add a new NPM_TOKEN since they're not scoped to packages.Why do you want this feature?
As @jawnsy brought up, this is cluttering the tags under the code-server package and makes it look ugly but also makes it hard for users to see actual versions.
Are there any workarounds to get this functionality today?
The current workaround is to just leave it as is.
Are you interested in submitting a PR for this?
Yes! But also open to mentor others who might be interested in doing this :)
The text was updated successfully, but these errors were encountered: