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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@studiocms/ui

v0.3.2

Published

The UI library for StudioCMS. Includes the layouts & components we use to build StudioCMS.

Downloads

393

Readme

@studiocms/ui

NPM Version Formatted with Biome Built with Astro

This is the UI library that we use to build StudioCMS.

To see how to get started, check out the documentation.

Contributing

We welcome contributions from the community! Whether it's bug reports, feature requests, or code contributions, we appreciate your help in making this project better.

Bug Reports and Feature Requests

If you encounter any bugs or have ideas for new features, please open an issue on our GitHub repository. When creating a new issue, please provide as much detail as possible, including steps to reproduce the issue (for bugs) or a clear description of the proposed feature.

Code Contributions

If you'd like to contribute code to this project, please follow these steps:

  1. Fork the repository and create a new branch for your contribution.
  2. Make your changes and ensure that the code follows our coding conventions and style guidelines.
  3. Write tests for your changes, if applicable.
  4. Update the documentation, if necessary.
  5. Commit your changes and push them to your forked repository.
  6. Open a pull request against the main repository, providing a clear description of your changes and their purpose.

We will review your contribution as soon as possible and provide feedback or merge it into the main codebase if everything looks good.

Please note that by contributing to this project, you agree to our Code of Conduct.

Thank you for your interest in contributing to this project!

Chat with Us

We have an active community of developers on the StudioCMS Discord Server. Feel free to join and connect with other contributors, ask questions, or discuss ideas related to this project or other StudioCMS projects.

Our ToolSet

For an up-to-date list of our main tools check out our .prototools file.

For more information about Proto checkout Proto's Website.

Licensing

MIT Licensed - StudioCMS 2024