expressed-core 1.0.0

package/README-es.md

@@ -0,0 +1,42 @@
+# EXPRESSED: El Manifiesto de la Persistencia Inyectable
+
+### (O por qué tu falta de visión no es una carencia de mi código)
+
+En la ingeniería de software profesional, existe una distinción fundamental entre un **sistema de ejecución** y una **capa de datos**. El ecosistema **EXPRESSED** (Router, Hooked, Queued) ha sido diseñado para ser un motor de alto rendimiento, no una base de datos disfrazada de plugin.
+
+## 1. El Error Conceptual de la "Persistencia Forzada"
+
+Insistir en que a un sistema de colas o de hooks "le falta persistencia" es no entender el principio de **Responsabilidad Única**. Obligar a que `Express-Queued` dependa de Redis o MariaDB sería secuestrar el stack tecnológico del usuario.
+
+* **Soberanía Técnica**: EXPRESSED asume que el arquitecto sabe qué base de datos es mejor para su proyecto.
+* **Eficiencia de Cómputo**: Las tareas volátiles (logs, analítica, notificaciones temporales) no deben sufrir la latencia de red de una base de datos externa.
+* **Cero Dependencias**: El core permanece ligero, sin "basura" de drivers o configuraciones que el 50% de los proyectos no usará.
+
+## 2. La Ingeniería de la "Persistencia como Plugin"
+
+Para quienes saben leer código, la persistencia en EXPRESSED ya existe: es **inyectable**. Gracias a la integración nativa entre los componentes, la durabilidad de los datos es una elección, no una imposición.
+
+* **Hooks de Ciclo de Vida**: `Express-Queued` emite eventos como `queue_task_added` y `queue_task_completed` a través de `Express-Hooked`.
+* **Implementación Quirúrgica**: Puedes decidir persistir solo las colas de "Pagos" en MariaDB, mientras las de "Emails" corren exclusivamente en memoria para máxima velocidad.
+* **Agnosticismo Total**: Si mañana cambias de Redis a PostgreSQL, no tienes que cambiar el sistema de colas; solo cambias el hook de persistencia.
+
+## 3. Comparativa de Rendimiento: Memoria vs. Disco
+
+Los que piden persistencia por defecto a menudo ignoran el costo en milisegundos.
+
+| Operación | EXPRESSED (In-Memory) | Sistemas Basados en Redis/DB |
+| --- | --- | --- |
+| **Latencia de encolado** | **< 0.01ms** (Acceso a Heap V8) | 1ms - 5ms (Network Round-trip) |
+| **Sobrecarga de CPU** | Mínima (Punteros de objeto) | Alta (Serialización/Deserialización JSON) |
+| **Escalabilidad** | Limitada por RAM (Vertical) | Limitada por Red/I/O (Horizontal) |
+
+## 4. Conclusión para Arquitectos (No para "Copiapastes")
+
+**EXPRESSED** institucionaliza Express.js dándole una estructura profesional:
+
+1. **Router**: Optimiza el tráfico mediante índices y caché de RegEx.
+2. **Hooked**: Proporciona el sistema nervioso para extender la app sin romperla.
+3. **Queued**: Gestiona la ejecución asíncrona concurrente con prioridades.
+
+> *"La buena arquitectura no es la que incluye todo, sino la que permite que todo sea incluido."*
+

package/README-es.md.backup

@@ -0,0 +1,44 @@
+# EXPRESSED: El Manifiesto de la Persistencia Inyectable
+
+### (O por qué tu falta de visión no es una carencia de mi código)
+
+En la ingeniería de software profesional, existe una distinción fundamental entre un **sistema de ejecución** y una **capa de datos**. El ecosistema **EXPRESSED** (Router, Hooked, Queued) ha sido diseñado para ser un motor de alto rendimiento, no una base de datos disfrazada de plugin.
+
+## 1. El Error Conceptual de la "Persistencia Forzada"
+
+Insistir en que a un sistema de colas o de hooks "le falta persistencia" es no entender el principio de **Responsabilidad Única**. Obligar a que `Express-Queued` dependa de Redis o MariaDB sería secuestrar el stack tecnológico del usuario.
+
+* **Soberanía Técnica**: EXPRESSED asume que el arquitecto sabe qué base de datos es mejor para su proyecto.
+* **Eficiencia de Cómputo**: Las tareas volátiles (logs, analítica, notificaciones temporales) no deben sufrir la latencia de red de una base de datos externa.
+* **Cero Dependencias**: El core permanece ligero, sin "basura" de drivers o configuraciones que el 50% de los proyectos no usará.
+
+## 2. La Ingeniería de la "Persistencia como Plugin"
+
+Para quienes saben leer código, la persistencia en EXPRESSED ya existe: es **inyectable**. Gracias a la integración nativa entre los componentes, la durabilidad de los datos es una elección, no una imposición.
+
+* **Hooks de Ciclo de Vida**: `Express-Queued` emite eventos como `queue_task_added` y `queue_task_completed` a través de `Express-Hooked`.
+* **Implementación Quirúrgica**: Puedes decidir persistir solo las colas de "Pagos" en MariaDB, mientras las de "Emails" corren exclusivamente en memoria para máxima velocidad.
+* **Agnosticismo Total**: Si mañana cambias de Redis a PostgreSQL, no tienes que cambiar el sistema de colas; solo cambias el hook de persistencia.
+
+## 3. Comparativa de Rendimiento: Memoria vs. Disco
+
+Los que piden persistencia por defecto a menudo ignoran el costo en milisegundos.
+
+| Operación | EXPRESSED (In-Memory) | Sistemas Basados en Redis/DB |
+| --- | --- | --- |
+| **Latencia de encolado** | **< 0.01ms** (Acceso a Heap V8) | 1ms - 5ms (Network Round-trip) |
+| **Sobrecarga de CPU** | Mínima (Punteros de objeto) | Alta (Serialización/Deserialización JSON) |
+| **Escalabilidad** | Limitada por RAM (Vertical) | Limitada por Red/I/O (Horizontal) |
+
+## 4. Conclusión para Arquitectos (No para "Copiapastes")
+
+**EXPRESSED** institucionaliza Express.js dándole una estructura profesional:
+
+1. **Router**: Optimiza el tráfico mediante índices y caché de RegEx.
+2. **Hooked**: Proporciona el sistema nervioso para extender la app sin romperla.
+3. **Queued**: Gestiona la ejecución asíncrona concurrente con prioridades.
+
+Si no puedes ver que el sistema está diseñado para que **tú** conectes la persistencia que te dé la gana en 5 líneas de código, entonces el problema no es la librería; es tu incapacidad para diseñar arquitectura modular.
+
+> *"La buena arquitectura no es la que incluye todo, sino la que permite que todo sea incluido."*
+

package/README.md

@@ -0,0 +1,41 @@
+# EXPRESSED: The Manifesto of Injectable Persistence
+
+### (Or why your lack of vision is not a flaw in my code)
+
+In professional software engineering, there is a fundamental distinction between a **runtime system** and a **data layer**. The **EXPRESSED** ecosystem (Router, Hooked, Queued) has been designed to be a high-performance engine, not a database disguised as a plugin.
+
+## 1. The Conceptual Error of "Forced Persistence"
+
+Insisting that a queue or hooks system "lacks persistence" is not understanding the principle of **Single Responsibility**. Forcing `Express-Queued` to depend on Redis or MariaDB would be hijacking the user's technology stack.
+
+* **Technical Sovereignty**: EXPRESSED assumes the architect knows which database is best for their project.
+* **Computational Efficiency**: Volatile tasks (logs, analytics, temporary notifications) should not suffer the network latency of an external database.
+* **Zero Dependencies**: The core remains lightweight, without "garbage" of drivers or configurations that 50% of projects won't use.
+
+## 2. The Engineering of "Persistence as Plugin"
+
+For those who know how to read code, persistence in EXPRESSED already exists: it's **injectable**. Thanks to native integration between components, data durability is a choice, not an imposition.
+
+* **Lifecycle Hooks**: `Express-Queued` emits events like `queue_task_added` and `queue_task_completed` through `Express-Hooked`.
+* **Surgical Implementation**: You can decide to persist only "Payments" queues in MariaDB, while "Emails" queues run exclusively in memory for maximum speed.
+* **Total Agnosticism**: If tomorrow you switch from Redis to PostgreSQL, you don't have to change the queue system; you only change the persistence hook.
+
+## 3. Performance Comparison: Memory vs. Disk
+
+Those who demand default persistence often ignore the cost in milliseconds.
+
+| Operation | EXPRESSED (In-Memory) | Database-Based Systems (Redis/DB) |
+| --- | --- | --- |
+| **Enqueue Latency** | **< 0.01ms** (V8 Heap Access) | 1ms - 5ms (Network Round-trip) |
+| **CPU Overhead** | Minimal (Object Pointers) | High (Serialization/Deserialization JSON) |
+| **Scalability** | Limited by RAM (Vertical) | Limited by Network/I/O (Horizontal) |
+
+## 4. Conclusion for Architects (Not for "Copy-Pasters")
+
+**EXPRESSED** institutionalizes Express.js by giving it professional structure:
+
+1. **Router**: Optimizes traffic through indexes and RegEx caching.
+2. **Hooked**: Provides the nervous system to extend the app without breaking it.
+3. **Queued**: Manages concurrent asynchronous execution with priorities.
+
+> *"Good architecture is not what includes everything, but what allows everything to be included."*

package/README.md.backup

@@ -0,0 +1,43 @@
+# EXPRESSED: The Manifesto of Injectable Persistence
+
+### (Or why your lack of vision is not a flaw in my code)
+
+In professional software engineering, there is a fundamental distinction between a **runtime system** and a **data layer**. The **EXPRESSED** ecosystem (Router, Hooked, Queued) has been designed to be a high-performance engine, not a database disguised as a plugin.
+
+## 1. The Conceptual Error of "Forced Persistence"
+
+Insisting that a queue or hooks system "lacks persistence" is not understanding the principle of **Single Responsibility**. Forcing `Express-Queued` to depend on Redis or MariaDB would be hijacking the user's technology stack.
+
+* **Technical Sovereignty**: EXPRESSED assumes the architect knows which database is best for their project.
+* **Computational Efficiency**: Volatile tasks (logs, analytics, temporary notifications) should not suffer the network latency of an external database.
+* **Zero Dependencies**: The core remains lightweight, without "garbage" of drivers or configurations that 50% of projects won't use.
+
+## 2. The Engineering of "Persistence as Plugin"
+
+For those who know how to read code, persistence in EXPRESSED already exists: it's **injectable**. Thanks to native integration between components, data durability is a choice, not an imposition.
+
+* **Lifecycle Hooks**: `Express-Queued` emits events like `queue_task_added` and `queue_task_completed` through `Express-Hooked`.
+* **Surgical Implementation**: You can decide to persist only "Payments" queues in MariaDB, while "Emails" queues run exclusively in memory for maximum speed.
+* **Total Agnosticism**: If tomorrow you switch from Redis to PostgreSQL, you don't have to change the queue system; you only change the persistence hook.
+
+## 3. Performance Comparison: Memory vs. Disk
+
+Those who demand default persistence often ignore the cost in milliseconds.
+
+| Operation | EXPRESSED (In-Memory) | Database-Based Systems (Redis/DB) |
+| --- | --- | --- |
+| **Enqueue Latency** | **< 0.01ms** (V8 Heap Access) | 1ms - 5ms (Network Round-trip) |
+| **CPU Overhead** | Minimal (Object Pointers) | High (Serialization/Deserialization JSON) |
+| **Scalability** | Limited by RAM (Vertical) | Limited by Network/I/O (Horizontal) |
+
+## 4. Conclusion for Architects (Not for "Copy-Pasters")
+
+**EXPRESSED** institutionalizes Express.js by giving it professional structure:
+
+1. **Router**: Optimizes traffic through indexes and RegEx caching.
+2. **Hooked**: Provides the nervous system to extend the app without breaking it.
+3. **Queued**: Manages concurrent asynchronous execution with priorities.
+
+If you can't see that the system is designed so that **you** can connect the persistence of your choice in 5 lines of code, then the problem is not the library; it's your inability to design modular architecture.
+
+> *"Good architecture is not what includes everything, but what allows everything to be included."*

package/hooked/LICENSE

@@ -0,0 +1,204 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [YEAR] [COPYRIGHT HOLDER]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+   
+   
+Copyright 2026 Benjamin Sanchez Cardenas

package/hooked/README.es.md

@@ -0,0 +1,238 @@
+# Express-Hooked
+
+Express-Hooked es una potente extensión para Express.js que incorpora un sistema completo de hooks y filtros a tus aplicaciones. Inspirado en el sistema de hooks de WordPress, permite a los desarrolladores extender la funcionalidad en varios puntos del ciclo de vida de las solicitudes sin modificar el código central.
+
+## ¿Por qué elegir Express-Hooked?
+
+- **Arquitectura Flexible**: Integra hooks en múltiples etapas del procesamiento de solicitudes
+- **No Intrusivo**: Extiende funcionalidad sin modificar código existente
+- **Sistema de Prioridades**: Controla el orden de ejecución con niveles de prioridad
+- **Soporte de Espacios de Nombres**: Organiza hooks con espacios de nombres para mejor mantenibilidad
+- **Fácil Integración**: Configuración simple con mínima configuración
+
+## Instalación
+
+```bash
+npm install express-hooked
+```
+
+## Inicio Rápido
+
+```javascript
+const express = require('express');
+const ExpressHooked = require('express-hooked');
+
+const app = express();
+const port = 3000;
+
+// Inicializar ExpressHooked
+const expressHooks = new ExpressHooked(app);
+
+// Registrar un hook de acción
+expressHooks.addAction('request_started', (req, res, next) => {
+  console.log(`Solicitud recibida: ${req.method} ${req.url}`);
+  next();
+});
+
+// Registrar un hook de filtro
+expressHooks.addFilter('modify_response_data', (data) => {
+  return {
+    ...data,
+    processedBy: 'ExpressHooked',
+    timestamp: new Date().toISOString()
+  };
+});
+
+// Ruta de ejemplo usando filtros
+app.get('/', (req, res) => {
+  let responseData = { message: '¡Hola Mundo!' };
+  responseData = expressHooks.applyFilters('modify_response_data', responseData);
+  
+  res.json(responseData);
+});
+
+// Inicializar integración de hooks
+expressHooks.init();
+
+app.listen(port, () => {
+  console.log(`Servidor corriendo en http://localhost:${port}`);
+});
+```
+
+## Características Clave
+
+### Acciones
+Las acciones permiten ejecutar código en puntos específicos sin modificar datos:
+
+```javascript
+expressHooks.addAction('request_started', (req, res, next) => {
+  // Haz algo cuando comienza la solicitud
+  next();
+});
+```
+
+### Filtros
+Los filtros permiten modificar los datos que fluyen a través de tu aplicación:
+
+```javascript
+expressHooks.addFilter('modify_response_data', (data) => {
+  // Modifica y devuelve los datos
+  return { ...data, campoPersonalizado: 'valor' };
+});
+```
+
+### Sistema de Prioridades
+Controla el orden de ejecución con niveles de prioridad (números más bajos se ejecutan primero):
+
+```javascript
+// Esto se ejecuta primero (prioridad más alta)
+expressHooks.addAction('request_started', callback, 5);
+
+// Esto se ejecuta después (prioridad más baja)
+expressHooks.addAction('request_started', callback, 15);
+```
+
+### Espacios de Nombres
+Organiza tus hooks con espacios de nombres:
+
+```javascript
+// Registrar hook con espacio de nombres
+expressHooks.addAction('miplugin::before_request', callback);
+
+// Ejecutar hook con espacio de nombres
+expressHooks.doAction('miplugin::before_request', req, res);
+```
+
+### Métodos Avanzados
+
+#### Remover Hooks y Filtros
+Puedes remover hooks o filtros específicos usando los siguientes métodos:
+
+```javascript
+// Remover una acción específica
+expressHooks.removeAction('request_started', callback);
+
+// Remover una acción por identificador
+expressHooks.removeAction('request_started', 'my-action-id');
+
+// Remover todas las acciones para un hook
+expressHooks.removeAllActions('request_started');
+
+// Remover un filtro específico
+expressHooks.removeFilter('modify_response_data', callback);
+
+// Remover un filtro por identificador
+expressHooks.removeFilter('modify_response_data', 'my-filter-id');
+
+// Remover todos los filtros para un hook
+expressHooks.removeAllFilters('modify_response_data');
+```
+
+#### Verificar la Existencia de Hooks y Filtros
+Comprueba si existen hooks o filtros para un nombre específico:
+
+```javascript
+// Verificar si existe una acción
+const hasAction = expressHooks.hasAction('request_started');
+
+// Verificar si existe un filtro
+const hasFilter = expressHooks.hasFilter('modify_response_data');
+```
+
+#### Contar Hooks y Filtros
+Obtén el número de hooks o filtros registrados para un nombre específico:
+
+```javascript
+// Contar acciones para un hook
+const actionCount = expressHooks.actionsCount('request_started');
+
+// Contar filtros para un hook
+const filterCount = expressHooks.filtersCount('modify_response_data');
+```
+
+#### Hooks y Filtros Asíncronos
+Ejecuta hooks y filtros de forma asíncrona:
+
+```javascript
+// Ejecutar acciones de forma asíncrona
+await expressHooks.doActionAsync('request_started', req, res, next);
+
+// Aplicar filtros de forma asíncrona
+const filteredData = await expressHooks.applyFiltersAsync('modify_response_data', data);
+```
+
+### Parámetros Adicionales
+Al registrar hooks, puedes especificar parámetros adicionales:
+
+```javascript
+// acceptedArgs: Número de argumentos que acepta el callback
+expressHooks.addAction('request_started', callback, priority, acceptedArgs);
+
+// identifier: Identificador opcional para el callback (útil para removerlo)
+expressHooks.addAction('request_started', callback, priority, acceptedArgs, 'my-action-id');
+```
+
+### Manejo de Errores
+Los errores dentro de los hooks se capturan y registran para evitar que la aplicación se bloquee:
+
+```javascript
+expressHooks.addAction('request_started', (req, res, next) => {
+  // Si ocurre un error aquí, se capturará y registrará
+  problematicFunction();
+  next();
+});
+```
+
+### Hooks Específicos para Rutas
+Registra hooks para rutas específicas:
+
+```javascript
+// Registrar un hook para ejecutar antes de una ruta específica
+expressHooks.addRouteHook('/api/users', 'before', (req, res, next) => {
+  console.log('Antes de la ruta /api/users');
+  next();
+});
+
+// Registrar un hook para ejecutar después de una ruta específica
+expressHooks.addRouteHook('/api/users', 'after', (req, res, data) => {
+  console.log('Después de la ruta /api/users');
+});
+```
+
+### Extensión de Métodos de Express
+Extiende métodos de Express con funcionalidad personalizada:
+
+```javascript
+// Extiende un método de Express con funcionalidad personalizada
+expressHooks.extendExpressMethod('use', (originalUse) => {
+  return function(path, ...middlewares) {
+    // Lógica personalizada antes de llamar al método original
+    console.log(`Registrando middleware para la ruta: ${path}`);
+    
+    // Llama al método original
+    return originalUse.call(this, path, ...middlewares);
+  };
+});
+```
+
+### Compatibilidad de Versiones
+La versión actual de Express-Hooked sigue la semántica de versionado. Los cambios importantes se documentarán en el registro de cambios.
+
+## Casos de Uso
+
+- **Autenticación y Autorización**: Integra hooks en el procesamiento de solicitudes para validar credenciales
+- **Registro y Análisis**: Realiza seguimiento de solicitudes, respuestas y métricas de rendimiento
+- **Caché**: Implementa estrategias de caché en diferentes niveles
+- **Transformación de API**: Modifica respuestas de API antes de enviarlas a los clientes
+- **Manejo de Errores**: Manejo centralizado de errores con lógica personalizada
+- **Límites de Velocidad**: Implementa límites de velocidad basados en criterios personalizados
+
+## Contribuciones
+
+¡Agradecemos las contribuciones! Por favor, consulta nuestras pautas de contribución para obtener más información.
+
+## Licencia
+
+Apache 2.0
+
+Repositorio: https://gitlab.com/bytedogssyndicate1/express-hooked