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

create-burdy-app

v2.1.0

Published

Create Burdy apps in one command

Downloads

15

Readme

Create Burdy App

The easiest way to create a Burdy application.

Overview

npm install -g create-burdy-app

create-burdy-app my-app
cd my-app/
npm run dev

Open http://localhost:4000 to view your running app. When you're ready for production, run npm run build then npm run start.

Start Coding Now

You don't need to install or setup Webpack or Babel. They come packaged with burdy, so you can just start coding.

After running create-burdy-app, you're good to go!

Getting Started

Installation

Install it once globally:

npm install -g create-burdy-app

Creating an App

To create a new app, run:

create-burdy-app my-app
cd my-app

It will create a directory called my-app inside the current folder. Inside that directory, it will generate the initial project structure and install necessary dependencies:

.
├── node_modules
├── project
│   ├── admin
│      ├── index.tsx 
│   ├── types
│      ├── types.d.ts 
│   ├── index.ts
├── docker-compose.yml
├── Dockerfile
├── package.json
├── tsconfig.json
└── [...]

Entry points in Burdy are based on the two files:

  • project/admin/index.tsx (Admin) is used for adding functionality on UI (React) side of the application.
  • project/index.ts (Server) index.ts is used for adding functionality to server side of application.

Out of the box, we get:

  • Automatic transpilation and bundling (with webpack and babel)
  • Hot code reloading
  • Production building script

Once the installation finishes, you can run some commands in your project:

npm run dev or yarn dev

Runs the app in the development mode. Open http://localhost:4000/admin to view it in the browser.

The page will reload if you make edits. You will also see any errors in the console.

npm run build or yarn build

Builds the app for production to the .burdy/build folder. It correctly bundles React in production mode and optimizes the build for the best performance.

npm run start or yarn start

Starts the application in production mode. The application should be compiled with `npm run build` first.

Now you're ready to code & deploy your app!

Acknowledgements

We are grateful to the authors of existing related projects for their ideas as inspiration: