How to implement custom middleware in Alosaur?

Create a class that implements the Middleware interface or use hooks with onPreAction, onPostAction, and onCatchAction. Attach it globally or to specific areas/controllers via app configuration or decorators.

Alosaur vs Oak: which is better for Deno?

Alosaur provides a structured, decorator-based framework with DI, ideal for complex applications, while Oak is minimalist and flexible. Choose Alosaur for large-scale projects and Oak for simpler, rapid development.

Can I use TypeScript with Alosaur?

Yes, Alosaur is built with TypeScript and fully supports it. The framework leverages TypeScript's type system for decorators and DI, making development type-safe.

How to handle errors in Alosaur applications?

Utilize hooks with the onCatchAction method to catch errors at various levels, or implement global error middleware to handle exceptions consistently across the application.

What template engines are compatible with Alosaur?

Alosaur supports any template engine; you can integrate popular ones like EJS or Handlebars by implementing the render interface, as shown in the examples on GitHub.

Is there a CLI for generating Alosaur projects?

Currently, Alosaur does not have an official CLI tool. Developers typically set up projects manually using Deno's module system, but community contributions might offer alternatives.

Open-Awesome

alosaur

MITTypeScriptv1.1.1

A Deno web framework built with ES decorators for modular, secure, and dependency-injected applications.

Visit Website GitHub

817 stars48 forks0 contributors

What is alosaur?

Alosaur is a web framework for Deno that uses ES decorators to structure applications with areas, controllers, and middleware. It provides built-in dependency injection, security features, and template rendering, solving the need for a modular and secure server-side framework in the Deno ecosystem.

Target Audience

Deno developers building structured web applications, APIs, or full-stack projects who prefer decorator-based syntax and dependency injection.

Value Proposition

Developers choose Alosaur for its comprehensive feature set, including security and DI out-of-the-box, and its use of modern ES decorators for clean, maintainable code in Deno environments.

Overview

Alosaur - Deno web framework with many ES Decorators

Use Cases

Best For

Building modular web applications with Deno
Creating APIs with decorator-based routing
Implementing authentication and authorization in Deno projects
Developing server-side rendered applications with template engines
Structuring large applications with dependency injection
Using middleware and hooks for request lifecycle management

Not Ideal For

Projects targeting Node.js or other JavaScript runtimes besides Deno
Teams that prefer functional programming patterns over class-based controllers and decorators
Applications deployed on Deno Deploy that require minimal overhead, where Alosaur Lite is recommended instead
Developers needing extensive third-party middleware or plugins, due to Deno's smaller ecosystem

Pros & Cons

Pros

Decorator-Based Routing

Uses ES decorators like @Get() to define routes and bind parameters, simplifying route management and reducing boilerplate code.

Built-in Dependency Injection

Automatically injects dependencies into controllers and hooks, promoting cleaner architecture and easier testing without external DI libraries.

Comprehensive Security Suite

Includes out-of-the-box support for authentication, authorization, sessions, and OAuth, reducing the need for additional security packages.

Modular Application Structure

Organizes code into areas and controllers, enabling scalable and maintainable project organization for large applications.

Cons

Deno-Exclusive Dependency

Locks applications into the Deno runtime, making migration to other platforms like Node.js challenging and dependent on Deno's development pace.

Heavy for Simple Use Cases

The structured approach with areas, DI, and decorators can be overkill for basic APIs or microservices, where lighter frameworks might be more appropriate.

Ecosystem Limitations

As a Deno framework, it faces a smaller package ecosystem compared to Node.js, potentially requiring custom implementations for some features.

Frequently Asked Questions

Related Projects

Hono

Web framework built on Web Standards

A middleware framework for handling HTTP with Deno, Node, Bun and Cloudflare Workers 🐿️ 🦕

Stars5,402

Forks240

Last commit2 months ago

drash

A microframework for building JavaScript HTTP applications. Runtime-agnostic. Strongly typed.

Stars1,067

Forks30

Last commit1 year ago

opine

Minimalist web framework for Deno ported from ExpressJS.

Stars849

Forks43

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub