new-package

To scaffold a new shared package in a monorepo, create the standard source and test directories, add package metadata, register the package in the workspace configuration, and run verification tests. This ensures the new library follows monorepo conventions and is properly integrated.

The standard directory structure for monorepo packages includes dedicated source and test directories, package metadata files, and workspace registration. Following this layout ensures the reusable library conforms to repository conventions and integrates seamlessly with existing applications.

Add a reusable library to a workspace configuration by placing it in the packages directory, updating the workspace settings to recognize the new path, and verifying that the repository registers the package name uniquely without duplicating existing functionality.

Yes, a new monorepo package requires documentation updates. After scaffolding and verifying the package, you must update the architecture overview so the new shared library is visible and discoverable to the rest of the team.

The best way to verify a newly scaffolded monorepo package is to run the placeholder test after workspace registration. This confirms the repository recognizes the package and that the directory structure follows monorepo conventions properly.

You should not use a monorepo package scaffold when adding a standalone application rather than a reusable library. This scaffolding process is specifically for shared packages under the packages directory, not for apps that do not need to be consumed by other workspace projects.