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

@expofp/ui

v3.23.2

Published

ExpoFP SDK internal: shared pure React UI components

Readme

@expofp/ui

Shared pure, presentational React components for the ExpoFP SDK. Bundled with the packages that depend on it — no separate install.

Scope rule: props-in, markup-out components only — no domain logic, no MobX stores, no data fetching, no side effects. Nothing here may know about floor plans, booths, exhibitors, or events, or import from a domain package. Components receive everything they render via props; stateful wiring (Containers) lives in the consuming package. The test: could it ship in a general-purpose React component library unchanged? If not, it belongs next to the domain that owns it.

Styling

Components import their own .scss, which expects the SDK's shared SCSS layer (design tokens, mixins, icon glyphs) via the @styles alias. The published package ships JS only — no compiled CSS and no .scss sources. It is therefore consumed from source by @expofp/floorplan's bundler (the @expofp/source export condition), which compiles the SCSS into its own output. @expofp/ui is an internal building block and is not intended to be styled standalone from its published dist.

src/styles (the primitives _vars, _utils, main, _icons) and public/fonts are the canonical home of this layer — @expofp/floorplan points its own @styles alias here instead of keeping a copy. If a third consumer ever needs it, split it into a dedicated @expofp/styles package; until then, one extra alias hop is simpler than a package with a single dependent.

  • Build: nx build ui
  • Test (unit): nx test ui
  • Test (stories, browser): nx test-storybook ui
  • Storybook (dev): nx storybook ui
  • Storybook (build): nx build-storybook ui
  • Lint: nx lint ui