📄️ Publish unscoped public package
As a dartpm user, you can create unscoped packages to use in your own projects and publish them to the dartpm public registry for others to use in their. Unscoped packages are always public and are refferd to by the package name only.
📄️ Publish scoped public package
To share your code publicly in a user or organization scope, you can publish public user-scoped or organization-scoped packages/plugins to the dartpm registry.
📄️ Publish private package
To share your code with a limited set of users or teams, you can publish private user-scoped or organizaition-scoped packages to the dartpm registry.
📄️ Package naming guidelines
When choosing a name for your package, choose a name that
📄️ Semantic versioning
To keep the dart ecosystem healthy, reliable, and secure, every time you make significant updates to the dart package you own, we recommend publishing a new version of the package with an updated version number in the pubspec.yaml file the follows the semantic versioning spec. Following the semantic versioning spec helps other developers who depend on your code understnad the extent of changes in a given version, and adjust their own code ig necessary.