semver VS react-native

You can then add a commit message to your check-in. Some developer teams follow the Conventional Commit specification when adding commit messages, which dovetails SemVer and makes it easier to publish release notes based on widely known standards.

But after reading this interesting Issue on the semver repo: https://github.com/semver/semver/issues/221 my opinion is changing. Using version 0.x indicates instability, true, but the reality is that some libraries are unstable.

In addition to what the siblings say, in case parent isn't aware of semantic versioning: https://semver.org/

Senamtic Versioning - https://semver.org/

It seems to me that a lot of people are forgetting that when updating to next major version of a package, breaking changes are expected - that's the whole point of major version number in SemVer [1]. What they actually want is seamless updates (or never changing APIs, but that not possible in most situations, and also not what you want as a package developer - you want to be able to correct your API design mistakes). That requires a lot of work from the package developers.

Look for example how people at Remix do it: breaking changes are hidden behind future flags [2], so you a user can turn them on one by one and adapt their code on gradually without surprises. Another solution is creating codemods for upgrades. But how many open-source package developers are willing do to this extra work?

Same story with peer dependencies - they're completely fine, if package developers know how to use them.

As always, don't be mad at React, don't curse Npm, it's not their fault. There is no great package without great effort.

[1] https://semver.org/

You can always check the official Semantic Versioning Specification.

Using Semantic Versioning for version control.

React Native 0.78 RC.0 Released

With a thriving community of over 2,700 contributors on GitHub and many more in other parts of the Internet, React Native has a healthy ecosystem that keeps on expanding. Its community encourages knowledge exchange, troubleshooting, and continuous improvement, making it an invaluable resource for developers worldwide. All of this is encouraged by Meta, who provides React Native with support and frequent updates.

React Native is the powerhouse for cross-platform mobile development. Write once, run everywhere, get native performance when you need it, enjoy hot reloading for rapid development, tap into a huge ecosystem of libraries and tools, and integrate with native modules when you need platform-specific features.

React Native is a powerful framework for building cross-platform mobile applications using JavaScript and React. Whether you're a seasoned developer or a beginner, starting a new React Native project can be both exciting and challenging. This guide will walk you through the essential steps, tools, and best practices to set up your React Native project efficiently and effectively.

支持 React、ReactNative 和 TypeScript。

Supports React, ReactNative, and TypeScript.

Official React Native Documentation

It was so comfortable with React Native and had a chance to work in the [email protected] (i tell this everyone 🥹)

React Native is an open-source mobile application development framework created by Facebook that enables developers to build mobile apps for iOS and Android using JavaScript and React. It allows for cross-platform development, meaning you can write code once and deploy it on both major mobile platforms, significantly reducing development time and resources. With more than 100k GitHub stars and a huge community, it is one of the leading frameworks for mobile app development.

Hybrid development frameworks, like React Native and Uno Platform, address some of the trade-offs between web and native apps by allowing developers to write code that works across platforms: