diesel-core
v2.2.3
Published
Web framework built on Web Standards
Maintainers
Readme
Read the docs
DieselJS
Diesel is a simple and lightweight HTTP server library for Bun.js that provides you with complete control over your API routes and middleware. It is designed to be intuitive and efficient, allowing you to quickly set up a server, define routes, and optimize important paths for faster response times. started this on 5th october 2024
Now Supports Node.js & Cloduflare adaptors
Installation
Install diesel-core via bun | npm | yarn | pnpm
npm install diesel-corebun add diesel-coreCode Example
import {Diesel} from "diesel-core"
const app = new Diesel()
const port = 3000
app.get("/", async (ctx:ContextType) => {
return ctx.text("Hello world...!",200)
// Note :- passing statusCode is optional
})
// Start the server
app.listen(port, () => {
console.log(`diesel is running on port ${port}`)
})HttpMethods
In Diesel there are almost all http methods that you can use
app.get() app.post() app.put()
app.patch() app.delete() app.any()
app.head() app.options() , app.onMethod(method,path,handler)Cloudflare workers
now you can use diesel.js for cloudflare workers apis
import {Diesel} from "diesel-core"
const app = new Diesel({
platform: 'cf',
logger: true
})
.get("/", (ctx) => ctx.text("Welcome to Diesel.js on Cloudflare Workers!"));
export default {
fetch: app.fetch()
}
Note make sure to add platform:'cf' & call fetch(), it gives you real fetch handler
Node.js adaptor
Now you can use Diesel.js for Node.js
import { Diesel } from "diesel-core"
import { serve } from 'diesel-core/node'
const app =
new Diesel({
logger:true
})
.get("/", (c) => {
return c.text(`hello from node diesel/`)
})
serve({
fetch: app.fetch(),
port: 3000
})CORS
Diesel supports CORS out of the box
import { cors } from "diesel-core/cors";
app.use(cors({
origin: ['http://localhost:5173', 'https://myapp.com'],
methods: ['GET', 'POST', 'PUT', 'DELETE'],
allowedHeaders: ['Content-Type', 'Authorization'],
credentials: true,
}));Filter and Route Security
Diesel provides a simple way to manage public and protected routes using the setupFilter() method. You can define specific routes to be publicly accessible, while all other routes require authentication or custom middleware.
How to Use the Filter
The setupFilter() method allows you to secure certain endpoints while keeping others open. Specify routes that should be publicly accessible using publicRoutes() + permitAll(), and apply authentication middleware to the remaining routes with authenticate().
Example Usage
import { Diesel } from "diesel-core";
import jwt from 'jsonwebtoken';
const app = new Diesel();
async function authJwt(ctx: ContextType): Promise<void | Response> {
const token = ctx.cookies?.accessToken;
if (!token) {
return ctx.json({ message: "Authentication token missing" }, 401);
}
try {
const user = jwt.verify(token, secret);
ctx.set('user', user);
} catch (error) {
return ctx.json({ message: "Invalid token" }, 403);
}
}
// Define routes and apply filter
app
.setupFilter()
.publicRoutes('/api/user/register', '/api/user/login', '/test/:id', '/cookie')
.permitAll()
.authenticate([authJwt]);
// Public route (no auth required)
app.get("/api/user/register", async (ctx: ContextType) => {
return ctx.json({ msg: "This is a public route. No authentication needed." });
});
// Protected route (requires auth)
app.get("/api/user/profile", async (ctx: ContextType) => {
const user = ctx.get("user");
return ctx.json({ msg: "You are authenticated!", user });
});
const port = 3000;
app.listen(port, () => {
console.log(`Diesel is running on port ${port}`);
});Filter Methods
- publicRoutes(...routes: string[]) : Routes passed here are public and require no authentication, including those with dynamic parameters (e.g., /test/:id).
.publicRoutes('/api/user/register', '/api/user/login', '/test/:id')- permitAll() : Marks the routes specified in
publicRoutes()as publicly accessible, bypassing authentication middleware.
.permitAll()- authenticate([fnc?: middlewareFunc]) : Applies one or more authentication middleware functions to all routes not listed in
publicRoutes().
Note : If you don't pass a middleware function to authenticate(), DieselJS will return an "Unauthorized" response by default.
.authenticate([authJwt])
.authenticate([authJwt, rateLimiter]) // chain multiple auth middlewares- authenticateJwt(jwt) : Built-in JWT filter. Requires
jwtSecretset inDieselOptions. Setsctx.get("user")automatically.
const app = new Diesel({ jwtSecret: "your-secret" });
app.setupFilter().publicRoutes('/login').permitAll().authenticateJwt(jwt);Use Case
Public Routes : Routes like
/api/user/registeror/api/user/loginare open to all users. Add them withpublicRoutes()+permitAll().Protected Routes : All other routes require authentication via
authenticate([authJwt])orauthenticateJwt(jwt).
Using Hooks in DieselJS
DieselJS allows you to enhance your request handling by utilizing hooks at various stages of the request lifecycle. This gives you the flexibility to execute custom logic for logging, authentication, data manipulation, and more.
Available Hooks
- onRequest: Triggered when a request is received.
- preHandler: Invoked just before the request handler executes.
- onSend: Called just before the response is sent to the client.
- onError : Executes if any error occurs
How to Define Hooks
To define hooks in your DieselJS application, you can add them directly to your Diesel instance. Here's how to set up and use each hook:
Example Usage
// onError hook: receives (error, path, req)
app.addHooks("onError", (error, path, req) => {
console.log(`Error on ${req.method} ${path}: ${error.message}`)
// optionally return a Response to override the default error response
})
// onRequest hook: receives ctx
app.addHooks("onRequest", (ctx) => {
console.log(`Request received: ${ctx.req.method} ${ctx.path}`);
})
// preHandler hook: receives ctx, return a Response to stop the request
app.addHooks("preHandler", (ctx) => {
const authToken = ctx.req.headers.get("Authorization");
if (!authToken) {
return new Response("Unauthorized", { status: 401 });
}
})
// onSend hook: receives ctx and the outgoing result Response
app.addHooks('onSend', async (ctx, result) => {
console.log(`Sending response with status: ${result.status}`);
return result; // return a modified response or the original
});Middleware example
No Need to call NonSense next() in Middleware
just dont return , if evrything goes right
async function authJwt (ctx:ContextType): Promise<void | Response> {
try {
const token = ctx.cookies?.accessToken
if (!token) {
return ctx.json({ message: "Authentication token missing" },401);
}
// Verify the JWT token using a secret key
const user = jwt.verify(token, secret);
ctx.set('user',user);
} catch (error) {
return ctx.json({ message: "Invalid token" },403);
}
}
// this is a global middleware
app.use(authJwt)
OR
app.use(authJwt,middleware2 , ...)
// path middleware example
app.use("/user",authJWT)
OR
// app.use(["/user","/home"],[authJWT,middleware2])
//means /user and /home has two middlewares
set cookies
app.get("/set-cookie", async(ctx:ContextType) => {
const user = {
name: "pk",
age: 22,
}
const accessToken = jwt.sign(user, secret, { expiresIn: "1d" })
const refreshToken = jwt.sign(user, secret ,{ expiresIn: "10d" })
const options = {
httpOnly: true,
secure: true,
maxAge: 24 * 60 * 60 * 1000,
sameSite: "Strict",
path: "/",
}
ctx
.setCookie("accessToken", accessToken, options)
.setCookie("refreshToken", refreshToken, options)
return ctx.json({msg:"setting cookies"})
})Render a HTML page
app.get("/render",async (ctx) => {
return ctx.file(`${import.meta.dir}/index.html`)
})redirect
app.get("/redirect",(ctx:ContextType) => {
return ctx.redirect("/");
})get params
You can use set Multiparams , like this
app.get("/product/:productId/:productName")app.get("/hello/:id/",(ctx:ContextType) => {
const id = ctx.params.id
const query = ctx.query // you can pass query name also , you wanna get
return ctx.json({ msg: "Hello", id });
})
