@stone-js/validation 0.8.11 → 0.8.13

package/dist/index.d.ts

@@ -6,7 +6,6 @@ export * from './decorators/Validate.js';
 export * from './decorators/Validation.js';
 export * from './decorators/ValidationSchema.js';
 export * from './errors/ValidationError.js';
-export * from './middleware/BlueprintMiddleware.js';
 export * from './middleware/validate.js';
 export * from './middleware/ValidateRouteMiddleware.js';
 export * from './options/ValidationBlueprint.js';

package/dist/index.js

@@ -595,42 +595,6 @@ const MetaValidateRouteMiddleware = {
     priority: 5
 };
 
-/**
- * Build-phase middleware: collect every class registered with `@ValidationSchema` into the registry.
- *
- * The same scan the router does for its route definitions, applied to this module's own key. After
- * it runs, `stone.validation.schemas` maps each alias to its class, so a route or a handler can name
- * a schema instead of importing it, and `@stone-js/openapi` can walk the registry to publish request
- * schemas without loading anything itself.
- *
- * @param context - The blueprint context.
- * @param next - The next blueprint middleware.
- * @returns The blueprint.
- */
-async function ValidationSchemaMiddleware(context, next) {
-    const registered = context
-        .modules
-        .filter((module) => hasMetadata(module, VALIDATION_SCHEMA_KEY))
-        .reduce((registry, module) => {
-        const { alias } = getMetadata(module, VALIDATION_SCHEMA_KEY, {});
-        return { ...registry, [alias ?? module.name]: module };
-    }, {});
-    if (Object.keys(registered).length > 0) {
-        context.blueprint.set('stone.validation.schemas', {
-            ...context.blueprint.get('stone.validation.schemas', {}),
-            ...registered
-        });
-    }
-    return await next(context);
-}
-/**
- * Meta blueprint middleware for schema discovery.
- */
-const MetaValidationSchemaMiddleware = {
-    module: ValidationSchemaMiddleware,
-    priority: 5
-};
-
 /**
  * Opt-in blueprint: import and register it to enable validation.
  *
@@ -644,11 +608,6 @@ const MetaValidationSchemaMiddleware = {
 const validationBlueprint = {
     stone: {
         validation: {},
-        blueprint: {
-            middleware: [
-                MetaValidationSchemaMiddleware
-            ]
-        },
         providers: [
             ValidationServiceProvider
         ],
@@ -754,4 +713,4 @@ function validate(rules) {
     };
 }
 
-export { MetaValidateRouteMiddleware, MetaValidationSchemaMiddleware, VALIDATE_KEY, VALIDATION_SCHEMA_KEY, Validate, ValidateRouteMiddleware, Validation, ValidationError, ValidationSchema, ValidationSchemaMiddleware, ValidationServiceProvider, Validator, defineValidationSchema, fromStandard, fromZod, isNativeSchema, isSchemaLike, isStandardSchema, isValidationSchema, isValidationSchemaClass, isZodLike, metadataKeyFor, readSource, resolveSchema, rulesOf, toValidationRules, validate, validateEvent, validationBlueprint };
+export { MetaValidateRouteMiddleware, VALIDATE_KEY, VALIDATION_SCHEMA_KEY, Validate, ValidateRouteMiddleware, Validation, ValidationError, ValidationSchema, ValidationServiceProvider, Validator, defineValidationSchema, fromStandard, fromZod, isNativeSchema, isSchemaLike, isStandardSchema, isValidationSchema, isValidationSchemaClass, isZodLike, metadataKeyFor, readSource, resolveSchema, rulesOf, toValidationRules, validate, validateEvent, validationBlueprint };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stone-js/validation",
-  "version": "0.8.11",
+  "version": "0.8.13",
   "description": "Framework-agnostic input validation for Stone.js. Define a schema once (Zod, Valibot, ArkType — anything Standard Schema) and validate it identically on the backend and the frontend.",
   "author": "Mr. Stone <evensstone@gmail.com>",
   "license": "MIT",
@@ -40,7 +40,7 @@
     "node": ">=18.17.0"
   },
   "peerDependencies": {
-    "@stone-js/core": "0.8.11"
+    "@stone-js/core": "0.8.13"
   },
   "devDependencies": {
     "@commitlint/cli": "^19.8.1",
@@ -62,7 +62,7 @@
     "typescript": "^5.6.3",
     "vitest": "^3.2.4",
     "zod": "^3.24.1",
-    "@stone-js/core": "0.8.11"
+    "@stone-js/core": "0.8.13"
   },
   "ts-standard": {
     "globals": [
@@ -75,7 +75,7 @@
     ]
   },
   "dependencies": {
-    "@stone-js/config": "0.8.11"
+    "@stone-js/config": "0.8.13"
   },
   "scripts": {
     "lint": "ts-standard src",

package/dist/middleware/BlueprintMiddleware.d.ts

@@ -1,18 +0,0 @@
-import { BlueprintContext, ClassType, IBlueprint, NextMiddleware, type MetaMiddleware } from '@stone-js/core';
-/**
- * Build-phase middleware: collect every class registered with `@ValidationSchema` into the registry.
- *
- * The same scan the router does for its route definitions, applied to this module's own key. After
- * it runs, `stone.validation.schemas` maps each alias to its class, so a route or a handler can name
- * a schema instead of importing it, and `@stone-js/openapi` can walk the registry to publish request
- * schemas without loading anything itself.
- *
- * @param context - The blueprint context.
- * @param next - The next blueprint middleware.
- * @returns The blueprint.
- */
-export declare function ValidationSchemaMiddleware(context: BlueprintContext<IBlueprint, ClassType>, next: NextMiddleware<BlueprintContext<IBlueprint, ClassType>, IBlueprint>): Promise<IBlueprint>;
-/**
- * Meta blueprint middleware for schema discovery.
- */
-export declare const MetaValidationSchemaMiddleware: MetaMiddleware<any, any>;