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

yarbs

v0.1.6

Published

i love [razzle](https://github.com/jaredpalmer/razzle), [cra](https://github.com/facebook/create-react-app), and of course [react-boilerplate](https://github.com/react-boilerplate)- but not all of my projects fit into those molds. i wanted something dead

Downloads

6

Readme

yet another react build system

motivation

i love razzle, cra, and of course react-boilerplate- but not all of my projects fit into those molds. i wanted something dead simple, with as little opinions as possible.

the main difference with yarbs is that it does not generate an app structure for you. it's literally just a wrapper around a webpack config, with helper scripts to run a dev server and build for production. that's it.

features

  • webpack-serve in place of webpack-dev-server
  • mdx ready
  • graphql ready
  • typescript ready
  • (node) server / proxy ready
  • fallback babel & eslint configs if no .babelrc or .eslintrc is detected

server-side is best optimized for koa, but you can use any node server framework.

anti-features

the only 2 opinions yarbs has:

  • client-side rendering only
    • because yarbs is server-ready, it's assuming you're building a web application- so we stick to client-side rendering for better performance.
  • does not parse CSS/SCSS
    • in favor of css-in-js design systems

installation

yarbs can be added to any react project.

$ yarn add yarbs

usage

add the start / build scripts to your package.json

"scripts": {
    "start:client": "yarbs run-client",
    "start:server": "yarbs run-server",
    "start": "yarbs start",
    "build": "yarbs build"
}

yarbs start will run the client and server scripts in parallel. you can use the individual client and server scripts if you want.

"scripts": {
    "start:client": "yarbs run-client",
    "start:server": "yarbs run-server"
}

directories

yarbs looks for common directory setups, and your app entry files must be located in one of them.

for client-side code, it looks for one of the following:

  • src/
  • client/
  • src/client/

for server-side code, it looks for one of the following:

  • server/,
  • api/
  • src/server
  • src/api

testing

yarbs does not have a test script nor is optimized for testing. thats up to you / your project.


init'd with golf ⛳️