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

bootstruct

v1.7.0

Published

Routing by structure. A name-convention web framework for Node.js.

Downloads

23

Readme

License: MIT Build Status

Bootstruct

Bootstruct is a web framework for Node, based on a folder-structure / file-name convention.

Routing by structure.

Table of contents

Overview

Creating web apps with Node requires wiring up our routes, we need to bind different URL paths to their handlers. We usually do that by declerative coding. Something like: bind('GET', '/api/books', handler).

With Bootstruct you don't code your routes. You just export your handler and name the file with its route name.

Technically, Bootstruct creates routes by parsing your routes folder and routes requests through that folder's structure, matching URLs to corresponding paths under that folder.

Meaning, to support routes like:

domain.com/
domain.com/A
domain.com/A/B
domain.com/A/B/C

your routes folder tree would generally look like:

├── routes
│   ├── index.js
│   └── A
│       ├── index.js
│       └── B
│           ├── index.js
│           └── C
│               └──index.js

 

Controling Request Flow

When working with middlware functions (express, connect...) you control request flow by binding 'this' route before 'that' route. The order in which you code your routes matters.

Bootstruct provides you with an onion-like layered app by leveraging the parental folder chain. So a request to /A/B/C would go through:

1. /
2. /A
3. /A/B
4. /A/B/C
5. /A/B
6. /A
7. /

Do you see the onion?

 

Naming Convention

Bootstruct uses files and folders with certain names as different hooks.

For example, to handle GET requests, name your handler file _get.js. To handle POST requests, name it _post.js.

You can create your own hooks

 

What Else?

  • Create your own hook
  • Handle dynamic url params (e.g. /A/B/whatever)
  • Extend Bootstruct's different prototypes and more.

 

Bootstruct:

  • [x] saves you from coding your routes.
  • [x] enforces a natural code separation by concept.
  • [x] provides you with great control over request flow.
  • [x] is extensible.

 

Start Using Bootstruct


Questions, suggestions, criticism, bugs, hugs, typos and kudos are all welcome.

taitu.dev (at) gmail dot com