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 🙏

© 2026 – Pkg Stats / Ryan Hefner

fles-xroutes

v2.0.1

Published

To install dependencies:

Readme

📚 FLES-JS XRoutes Documentation

🔷 How to Use

1. Install Package

npm install fles-js-xroutes

2. Basic Setup

import express from 'express'
import { XRoutes, XMiddleware } from 'fles-js-xroutes'

const app = express()

await XRoutes.createServer(app, { dir: 'src' })

app.listen(3000)

3. Folder Structure

project/
├── src/
│   └── routes/           <- MUST be named "routes"
│       ├── users/
│       │   └── controller.ts
│       └── admin/
│           └── controller.ts

4. Controller Format

A. Function Format

export async function GET(req: Request, res: Response) {
    res.json({ message: 'Hello' })
}

B. Class Format

export default class UserController {
    static async getUsers(req: Request, res: Response) {
        res.json({ users: [] })
    }
}

🔷 Middleware Features

1. Basic Middleware Setup

XMiddleware.setup({
    global: [
        async (req, res, next) => {
            console.log('Request received!')
            next()
        }
    ]
})

2. Route Specific Middleware

XMiddleware.setup({
    routes: {
        '/admin/*': [
            async (req, res, next) => {
                console.log('Admin route!')
                next()
            }
        ]
    }
})

3. Method Specific Middleware

XMiddleware.setup({
    routes: {
        '/api/users': {
            GET: [middleware1],
            POST: [middleware2],
            PUT: [middleware3],
            DELETE: [middleware4]
        }
    }
})

🔷 Route Patterns

1. Basic Pattern

  • /admin -> Exact match
  • /api -> Exact match

2. Wildcard

  • /admin/* -> All paths under /admin
  • */admin -> All paths ending with admin
  • */admin/* -> All paths containing admin in the middle

3. Dynamic Route

  • users/[id] -> /users/:id
  • posts/[slug] -> /posts/:slug

4. Match Examples

'/admin/*' Matches:

  • /admin/users
  • /admin/settings
  • /admin
  • /api/admin

🔷 Tips & Tricks

1. Middleware

  • Global runs first
  • Route-specific runs second
  • Method-specific runs last
  • Can combine multiple middleware

2. Best Practices

  • Create reusable middleware
  • Always validate input
  • Handle errors properly
  • Use TypeScript for stability
  • Clear documentation for team

3. Error Handling

  • Always use try-catch
  • Return error with clear description
  • Error logging is important
  • Handle async errors carefully

4. Performance

  • Use cache when needed
  • Minimize middleware quantity
  • Optimize database calls
  • Monitor response time

🔷 Automatic Error Handler

1. Basic Setup

Create an errorHandler.ts file in the src/ folder:

import { Request, Response, NextFunction } from 'express'

export const errorHandler = (err: any, req: Request, res: Response, next: NextFunction) => {
    // Your error handling logic here
    res.status(500).json({ 
        error: err.message || 'Internal Server Error' 
    })
}

2. How It Works

  • XRoutes automatically detects the errorHandler.ts file
  • No manual setup needed in index
  • Error handler will be active for all routes
  • Best practice for handling all errors

3. Error Handler Tips

  • Differentiate errors by status code
  • Log errors to file/database
  • Don't expose stack trace to client
  • Handle async errors properly

🔷 Full Example

import express from 'express'
import { XRoutes, XMiddleware } from 'fles-js-xroutes'

const app = express()

// Basic middleware
app.use(express.json())

// Setup middleware
XMiddleware.setup({
    global: [
        async (req, res, next) => {
            console.log('Request received!')
            next()
        }
    ],
    routes: {
        '/admin/*': [
            async (req, res, next) => {
                console.log('Admin route!')
                next()
            }
        ],
        '/api/users': {
            GET: [
                async (req, res, next) => {
                    console.log('Getting users!')
                    next()
                }
            ]
        }
    }
})

// Start server
await XRoutes.createServer(app, { dir: 'src' })

app.listen(3000, () => {
    console.log('Server running on http://localhost:3000')
})