Closed mindplay-dk closed 6 years ago
@mindplay-dk Can you describe the process to make this possible?
The link seems to explain it? I don't know npm very well tbh.
@mindplay-dk I finally figured it out. I didn't need to use dist-tag. What one needs to do is is:
This will publish a new version of your package that can only be installed with npm i picodom@next
.
That's all. The dist-tag command is there to help you manage your published tags, listing them, adding or removing them, not publishing.
Oh, cool! Thanks for explaining it :-)
@JorgeBucaran I'm not completely sure, but I think the way to do this is by having a 2.0
branch (or next
branch) where you work on this next version and then publish using --tag next
, as you did.
I think now you can't continue to work on 1.x on master and publish further updates… :(
@acstll You are right Arturo. 😆
Thank for helping me understand the final piece of the puzzle, we'll do it right from now on (after 2.0.0).
@JorgeBucaran no problem. Open source FTW 😊
Could we have a dist-tag for
picodom@next
please?So we can more easily help beta-test the next major version, updating examples, etc. before release.