From node_modules to Your Project
LPM extracts complete, readable source files directly into your project directory. Components, styles, utilities. All yours to customize.
Unlike minified npm packages or compiled binaries, you receive clean, readable source files for JS or Swift projects. It’s the flexibility of shadcn/ui generalized for every library, design system, and starter kit you use.
Tailored to Your Stack
Authors define the logic; the CLI handles the resolution. Choose your framework, icons, or providers through interactive prompts before the code even touches your disk.
Configure Once, Install Anywhere
Authors use lpm.config.json to define interactive prompts for the consumer. Pick your styling, provider, or features, and the CLI resolves the rest in real-time.
LPM uses a condition system to map the exact file variants you need based on your project's unique setup, and conditional dependencies that auto-install based on your choices.
Why Source Code?
Because a black-box dependency you can't modify isn't really yours.
Full Ownership, Zero Lock-In
The code lives in your project, not hidden in a deep dependency tree. Read it, fork it, or fix it - you have ultimate control over every line of logic you ship.
Full Customization
Change colors, fonts, and logic directly in your source. Adapt every package to your specific brand and architecture without hacks or overrides.
No Hidden Dependencies
See exactly what code you're running with zero surprises. No minified bundles or supply chain concerns - just transparent, valid source code.
Design System Distribution
Ship an entire design system that buyers can theme to their own brand. Not a library they import, but a foundation they truly own.
Learn from Code
Reference implementations, starter kits, and tutorials where the source IS the product. Install, read, learn.
For Authors
Three configuration primitives. Combine them to ship packages that adapt to any buyer's stack.
Condition-Based Logic
Deliver specialized code without the technical debt. Use high-level conditions to swap providers, styling frameworks, or features in real-time.
Native Source Delivery
Ship valid, testable code with full IDE support. LPM automatically resolves and maps the correct file variants to the project at install time.
Smart Dependency Resolution
Define which npm or LPM packages are needed based on config choices. The CLI auto-installs the right ones for the buyer's stack.
Frequently Asked Questions
How are updates handled?
Source code delivery trades automatic updates for full ownership. When the author publishes a new version, you can diff and merge changes into your customized copy. This is a deliberate trade-off: you get code you can modify, not a black box that updates itself.
Can I customize the delivered code?
Yes, that's the entire point. The source code is delivered into your project directory, not node_modules. You own it, modify it, and maintain it. Change colors, refactor components, or adapt it to your architecture.
What are presets?
Presets are author-defined configuration options (like style, color theme, or provider) that are applied at install time. The CLI walks you through choices interactively, then delivers customized source code based on your selections.
How do Source Packages differ from a standard lpm install?
Standard packages are managed as external, immutable modules. Source Packages are injected directly into your project tree. It’s the difference between using a tool and owning the blueprint. Use standard installs for utilities you just need to work; use Source Packages for the core components and logic you need to customize, audit, and own forever.
Can I sell source-code-delivered packages?
Yes. Combine source code delivery with Marketplace licensing to sell UI components, templates, design systems, or starter kits with full source code access.
