Paket Yönetimi (NPM/Yarn)

Package managers like NPM (Node Package Manager) and Yarn are essential tools in modern software development. They automate the process of finding, installing, updating, and managing external code libraries and dependencies.

Instead of manually downloading files, you simply tell the package manager what you need, and it handles the rest!

Design systems are collections of reusable UI components and guidelines. To truly be 'reusable' across many different projects and teams, these components need to be easily distributable.

Package managers provide the perfect solution:

• Distribution: Make your component library available to all applications.
• Consistency: Ensure all projects use approved, consistent versions.
• Updates: Easily roll out bug fixes or new features to consumers.
• Dependency Management: Handle your library's own requirements.

In the JavaScript ecosystem, NPM and Yarn are the two dominant package managers. While they share the same goal, they have different command structures and performance characteristics.

• NPM: The default package manager for Node.js, widely adopted and robust.
• Yarn: Created by Facebook, often praised for faster installations and improved security features.

Both primarily manage your project's package.json file and the node_modules directory.

To turn your component library into a shareable package, you need a package.json file. This file is the manifest for your project, containing metadata like its name, version, and dependencies.

You can create this file interactively using the following commands:

For a component library, specific fields in package.json are critical for proper distribution and consumption:

• name: A unique identifier for your package (e.g., @myorg/design-system).
• version: The current version, following Semantic Versioning (SemVer).
• main: Specifies the entry point file for your package (e.g., dist/index.js).
• files: An array of files or directories to include when your package is published.
• private: true: Prevents accidental publishing to a public registry.

Your component library might rely on other packages. package.json allows you to specify different types of dependencies:

• dependencies: Packages absolutely required for your library to run (e.g., a utility library).
• devDependencies: Packages only needed during development, testing, or building (e.g., a testing framework, a bundler like Webpack).
• peerDependencies: Dependencies that your *consumers* are expected to provide (e.g., React if your components are React components). This prevents multiple versions of the same dependency.

Once your component library is built and configured (e.g., compiled to dist/index.js), you can publish it. This makes it available for others to install.

You typically publish to a package registry:

• Public Registries: Like the official npm registry, for open-source or widely shared packages.
• Private Registries: For internal company design systems, ensuring privacy and control (e.g., GitHub Packages, Azure Artifacts, private npm).

First, log in, then build your library, and finally publish:

In an application project that needs to use your design system, consuming the published package is simple. You just install it like any other dependency using its name.

Once installed, you can import and use the components:

Package managers rely on Semantic Versioning (SemVer), a standard for version numbers like MAJOR.MINOR.PATCH (e.g., 1.2.3). It communicates the nature of changes in each release:

• MAJOR (1.0.0 -> 2.0.0): Indicates backward-incompatible API changes. Consumers might need to update their code.
• MINOR (1.0.0 -> 1.1.0): New features added, but backward-compatible. Existing code should still work.
• PATCH (1.0.0 -> 1.0.1): Backward-compatible bug fixes. No new features, no breaking changes.

Always increment your version number according to SemVer rules before publishing!

We've explored how package managers like NPM and Yarn are vital for design systems. They enable you to:

• Initialize and configure your component library as a package.
• Manage different types of dependencies (dependencies, devDependencies, peerDependencies) effectively.
• Publish your library to public or private registries for others to use.
• Seamlessly consume shared components in applications using simple install commands.
• Understand and apply Semantic Versioning (SemVer) for clear and predictable updates.

Mastering package management is key to maintaining a scalable, consistent, and easily distributable design system!