Back us on Patreon for as little as $5 to get access to our first beta release this Friday!
Sharing code shouldn't be hard.
Transpilers, bundlers, type declarations, export mapping, modern browser optimizations, legacy browser support, unnecessary file trimming...
Open source contributors have to put up with a lot of bullsh!t just to share their code with the world.
A new take on package management.
Pika handles formatting, configuring, building and publishing every package on the registry, so that individual authors don't have to.
A registry that understands your source code is able to perfectly-configure your package for you. Pika builds your package to run everywhere, and you spend less time messing with boilerplate tooling. Win win!
For this new ecosystem to work, we needed a consistent, universal dev experience for every package on the registry. A universal package editor guarantees your package can't import or do anything Node.js specific that would require a bundler/tooling to use in the browser.
So we created Pika Code. Pika Code is a package code editor that gives you a hosted, easy-to-use, zero-config dev experience for every package on the registry. It takes care of all of your tooling for you, and connects directly with the registry for easy publishing.
Pika? NPM? Why not both.
Every Pika package is automatically published to npm. Your users can install your latest releases from npm, or import them directly from our global registry CDN.
A more secure registry.
No matter how well you secure your own codebase, external dependencies pose a security threat to everyone.
Pika protects the safety of the entire ecosystem by controlling the publish step. Pika publishes each package directly from source, so malicious or hacked authors can't skip code review or sneak malicious code unnoticed into the registry.