Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2024 – Pkg Stats / Ryan Hefner

umca

v0.8.0

Published

2 years ago

<div align="center">A simple zero-runtime serve-side rendering framework</div>

Downloads

4

0High
0Medium
0Low

Umca

Get started

The best way to begin developing with Umca is with npx:

npx umca create yourprojectname
cd yourprojectname

What Umca does and doesn't do

:white_check_mark: Takes JSX files that you wrote and compiles them into plain HTML
:white_check_mark: Automatically creates pages for (and only for) JSX files that are linked to with an <a> tag
:white_check_mark: Automatically adds prefetch hints to <head> if a page has internal links
:white_check_mark: Allows to import Markdown files from JSX files and automatically converts them to HTML
:white_check_mark: Comes with Tailwind CSS
:white_check_mark: Ships zero Javascript to the client

:x: Does not handle any user interactions. You have to bring your own JS
:x: Not an SPA (at least not yet)

Developing with Umca

Run yarn build or npm build to (re)compile your JSX
Run yarn start or npm start to locally host the public folder

/src

This is where all of your JSX files should be. Note that at least one of them must be named index.jsx, which is an entry file.

/pages

Umca allows you to import .md files right in your components. Put .md files in this folder.

CSS

Umca is equipped with Tailwind CSS. This means you only need to add existing (utility) classes to your elements and no CSS files are needed. This makes the framework highly opinionated. However, since pages are build with (reusable) components in Umca, you can both keep your design atomic AND avoid scope problems because all classes are just utilities.