node: dist-tag not recorded in package.json

I’ve been using prereleases recently and versioning works great, but I noticed that when I set that property the publishConfig tag property does not get set. I imagine the --tag flag is maybe getting used in a release workflow, but if you’re not using workflows, it would be nice for the supplied dist-tag to be tracked in the package.json.

Edit: I had prerelease in my head, but what I really meant was the npmDistTag option. prerelease specifically handles version suffix, so I did not expect it to set the dist-tag. It is my expectation that npmDistTag should, however, set the dist tag in a way that leads to a release being tagged with that dist-tag.

Is there a good reason it’s not being tracked in the package.json?

[dytyniuk]

@mrgrain I’m not saying, that we cannot start and finalize the release process “in the Cloud”. I am going to find this out literally now with my team 😃

My sincere expectation is that once the Merge Request is merged into the main branch, the CI will take care of the release process 🤞

Even if that configuration is not built by projen, having a straightforward action plan would be already a huge gain.

[mrgrain]

Although the projen is a kick-ass tool, TS/JS devs are taken away from their usual package managers (npm or yarn). Meaning they have to update .projenrc.js manually to have the package in their package.json. And even if they add a package via npm/yarn install, that will be gone after another npx projen run.

Yes that certainly is a trade-off. I could see a projen add <package> happen in future, but it’s blocked by #356