Holy moly, I'm literally building a component library for a client at work right now (never did anything like it in my life). This video couldn't have happened at a better time for me haha Extremely helpful as always, thanks so much!
This is a beuatiful explanation and walk through. I never thought I would be so engaged and interested in SemVer. I am doing freecodebootcamp, back end developer course/certification and have been learning how to make my own local server and now this regarding version. I play videogames, and seeing how versions play into breakchanges, minors, pathes and majors, makes so much sense now :) Thank you for this. I learned so much. Thank you :)
I watched a few of your videos not too long ago and loved it, but just now it took me like (excruciating) 5 minutes to find it because I couldn't remember the name. Lots of content in the internet these days hahaha
Hi thanks for the video.. i have one problm like when i am running on my feature branch the Tag version is 1.0.1, whn merging with the Develop Branch its getting changed to 271.1.0, but i want to be with 1.0.1 version for the Client SDK and the Data N Service Dll... but why its getting changed? any idea
I wasn't able to watch the entire video yet, so I'm not sure if this gets answered. Let's say I make a minor change to the codebase that isn't a new feature or a bugfix, and therefore shouldn't break the version, do I increment the version as a minor a patch?
Do you have an example in mind? I haven't ever run into a situation which isn't one of those categories. If you are upgrading anything at all, that's a feature. If you are fixing anything at all, that's a patch. However, if you are thinking about something like a refactor where the code is better but nothing changed for your user, you wouldn't bump the version at all because it doesn't affect the user.
Great video, thank you. As a follow up, can you make a video on semantic-release or any other package, which makes managing this tagging and versioning easier, than manually bumping up version when releasing a package
Great question, the semver standard says you should start with `0.1.0` until you get to the first stable version, then you'd update to `1.0.0`. In reality, people do all sorts of stuff, but that's the recommended pattern.
I don't, so it is unlikely I'd have one anytime soon, sorry. I like to dabble in all the frameworks but I don't make videos on anything I haven't used a decent amount.
JS Jesus is back !
Very nice to see semantic versioning in real world action by a person who has a solid understanding of the system. Thank you!
Kind words, thank you.
Holy moly, I'm literally building a component library for a client at work right now (never did anything like it in my life). This video couldn't have happened at a better time for me haha Extremely helpful as always, thanks so much!
That's awesome. I've been considering making some videos on design systems/component libraries, but it's a lot of work.
This is a beuatiful explanation and walk through. I never thought I would be so engaged and interested in SemVer. I am doing freecodebootcamp, back end developer course/certification and have been learning how to make my own local server and now this regarding version. I play videogames, and seeing how versions play into breakchanges, minors, pathes and majors, makes so much sense now :) Thank you for this. I learned so much. Thank you :)
Thanks for this awesome value bomb
Wow! Excellent examples to show the utility of SemVer.
Also, I learned something new about npm again - thank you.
I'm happy to hear it was helpful.
I finally know what ^ and ~ means :) THanks
Great tutoring skill you have. You should make more videos with same breakdown examples. Keep it up
Thank you.👍
Great video.
What font do you use throughout the video? Thanks.
Thank you for the comprehensive tutorial!
I watched a few of your videos not too long ago and loved it, but just now it took me like (excruciating) 5 minutes to find it because I couldn't remember the name. Lots of content in the internet these days hahaha
That's funny. I've been there before.
very informative video, thank you ❤️!
Omg, you deserve more views! I suggest you to put an attractive thumpnail. the content is so good to know! Thanks a lot
Thank you
this is owesomeeeeeeeeeeeee
Hi thanks for the video.. i have one problm like when i am running on my feature branch the Tag version is 1.0.1, whn merging with the Develop Branch its getting changed to 271.1.0, but i want to be with 1.0.1 version for the Client SDK and the Data N Service Dll... but why its getting changed? any idea
Sorry, I don't have enough details of the intentions to figure that out. I hope you've had some luck figuring it out by now.
@@SwashbucklingwithCode ok thanks.. for the reply.
I wasn't able to watch the entire video yet, so I'm not sure if this gets answered. Let's say I make a minor change to the codebase that isn't a new feature or a bugfix, and therefore shouldn't break the version, do I increment the version as a minor a patch?
Do you have an example in mind? I haven't ever run into a situation which isn't one of those categories. If you are upgrading anything at all, that's a feature. If you are fixing anything at all, that's a patch.
However, if you are thinking about something like a refactor where the code is better but nothing changed for your user, you wouldn't bump the version at all because it doesn't affect the user.
Great video, thank you. As a follow up, can you make a video on semantic-release or any other package, which makes managing this tagging and versioning easier, than manually bumping up version when releasing a package
Sure, I will add it to the list when I get started making videos again. In the meantime, I use changeset as my favorite versioning solution.
very useful
Nice.
Does the version start at 0.0.0 or 1.0.0?
Great question, the semver standard says you should start with `0.1.0` until you get to the first stable version, then you'd update to `1.0.0`.
In reality, people do all sorts of stuff, but that's the recommended pattern.
do you use vite? will you do a video on it?
I don't, so it is unlikely I'd have one anytime soon, sorry. I like to dabble in all the frameworks but I don't make videos on anything I haven't used a decent amount.
Thanks, can you do a new video on package lock?
Now I understand
Long time 🧐. Was waiting for ur videos.
Thank you for waiting. It's been a busy time for me.
Thanks john wick!!