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

@landtrustinc/design-system

v1.2.51

Published

Design system components for LandTrust applications

Readme

@landtrustinc/design-system

Design system components for LandTrust applications.

Storybook

📦 Installation

npm install @landtrustinc/design-system react-loading-skeleton

🚀 Setup

Required CSS Imports

⚠️ Important: You must import the following CSS files in your app's entry point (e.g., _app.js or _app.tsx for Next.js):

// pages/_app.tsx (Next.js) or main entry file
import '@landtrustinc/design-system/dist/variables.css';
import 'react-loading-skeleton/dist/skeleton.css';

Why?

  • The design system uses react-loading-skeleton for loading states in some components
  • Next.js and other frameworks require global CSS to be imported in the app entry point, not from npm packages
  • This prevents build errors and ensures proper styling

Next.js Configuration

If you're using Next.js, make sure these imports are at the top of your pages/_app.tsx or pages/_app.js:

import 'react-loading-skeleton/dist/skeleton.css';
import '@landtrustinc/design-system/dist/variables.css';

// ... rest of your imports

📖 Usage

import { Button, Box, Typography } from '@landtrustinc/design-system';

function App() {
  return (
    <Box>
      <Typography variant="h1">Hello World</Typography>
      <Button variant="primary">Click Me</Button>
    </Box>
  );
}

🎨 Styling

Following Figma styles try to use tokens from variables.css. Avoid using colors from the theme (these are legacy).

Keep the styles in separate file *.styles.ts

🔧 Development

npm run dev       # Start development server
npm run build     # Build package
npm run storybook # Run Storybook

📦 Publishing

npm build
npm version patch/minor/major
npm publish

📝 TODO

  • [ ] Migrate to Changesets - Replace manual version bumping with Changesets for automated versioning and changelog generation. This would prevent version conflicts and streamline the release process.