npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@placti/cli

v1.0.18

Published

CLI for building and deploying Placti federated remotes

Downloads

105

Readme

@placti/cli

CLI for building and deploying Placti federated remotes to S3/Garage.

Native Federation and esbuild are bundled — partners only need @placti/cli.

Install

npm i -D @placti/cli

Federation config (required)

Create federation-config.json in the project root (FederationConfig: name + exposes):

{
  "name": "myPartnerRemote",
  "exposes": { "./App": "./src/remote.tsx" },
  "shared": {},
  "features": { "ignoreUnusedDeps": true }
}

name must match remoteConfig.name when the feature is registered on Placti. It becomes the S3/Garage bucket name on deploy.

Commands

placti build-react

placti build-react [--dist ./dist] [--ts-config tsconfig.json]
placti build-react --watch
placti build-react --serve [--port 4202]

Reads federation-config.json, runs Native Federation + esbuild, writes dist/remoteEntry.json + chunks.

  • --watch — rebuild on change (process stays alive)
  • --serve — serve dist/ over HTTP (implies --watch); use behind a local reverse-proxy that maps /remote/{name}/latest/* to this port

placti deploy

placti deploy \
  --release v1.2.3 \
  --endpoint https://storage.platform.example.com \
  --access-key $PLACTI_ACCESS_KEY \
  --secret-key $PLACTI_SECRET_KEY

Remote name / bucket come from remoteEntry.json in the dist directory (no --name).

--dist points at the folder that contains remoteEntry.json. React remotes use the default ./dist. Angular CLI output is nested — pass the browser folder:

placti deploy --dist dist/angular-remote/browser --release v1.2.3 ...

Versioned releases upload to releases/{release}/ then swap latest/.

Mutable preview channel (does not touch latest/):

placti deploy --release preview ...

Wipes preview/ in the bucket and uploads the new dist there. Point a feature URL at /remote/{name}/preview/remoteEntry.json when you want that channel (not wired into Placti seeding by default).

Env equivalents: PLACTI_RELEASE, PLACTI_ENDPOINT, PLACTI_ACCESS_KEY, PLACTI_SECRET_KEY, PLACTI_REGION.

Use --dry-run to validate and preview without uploading.

Programmatic usage

import { buildRemote } from '@placti/cli/build';
import { deploy } from '@placti/cli/deploy';