@nestia/core 14.0.0 → 14.0.2

package/src/options/IResponseBodyStringifier.ts

@@ -6,25 +6,132 @@ export type IResponseBodyStringifier<T> =
   | IResponseBodyStringifier.IAssert<T>
   | IResponseBodyStringifier.IValidate<T>
   | IResponseBodyStringifier.IValidateLog<T>;
+/**
+ * The serializer that the transform passes to `TypedRoute` and `EncryptedRoute`
+ * for the JSON text of the response body.
+ *
+ * The literal `type` field selects which typia function generated it:
+ * `stringify` (no validation), `is`, `assert`, `validate`, or `validate.log`.
+ * `get_path_and_stringify` turns a failing validation into a 500 response,
+ * except `validate.log`, which logs the failure and answers with
+ * `JSON.stringify` of the data.
+ *
+ * @evidence contracts/common.md#principled-implementation The union is discriminated by the literal `type`, so the runtime selects the serializer with one comparison; the five variants are the typia stringify families, of which four validate the data and one does not.
+ * @evidence contracts/common.md#clear-and-simple-design Five variants, one per typia function family, with no shared base because each function has a different shape.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior; the runtime rejects an unknown `type` with an error instead of accepting it.
+ * @evidence contracts/common.md#meaningful-documentation The comment names the decorators that receive the serializer and the response each variant produces on a failed validation.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+ */
 export namespace IResponseBodyStringifier {
+  /**
+   * Serializer generated from `typia.json.stringify`, without validation.
+   *
+   * @evidence contracts/common.md#principled-implementation The variant tags a function that serializes the data as it is, so a value of the wrong type is serialized as far as its shape allows without this variant performing validation.
+   * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+   * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+   */
   export interface IStringify<T> {
     type: "stringify";
+    /**
+     * The generated function of the variant, taking the response data.
+     *
+     * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and the runtime uses the result as the response body as it is.
+     * @evidence contracts/common.md#clear-and-simple-design One function member.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+     * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     stringify: (input: T) => string;
   }
+  /**
+   * Serializer generated from `typia.json.isStringify`.
+   *
+   * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the serialized text, or `null` when the data is not of the type; `null` becomes a 500 `InternalServerErrorException` with a fixed message.
+   * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+   * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+   */
   export interface IIs<T> {
     type: "is";
+    /**
+     * The generated function of the variant, taking the response data.
+     *
+     * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the serialized text or `null`.
+     * @evidence contracts/common.md#clear-and-simple-design One function member.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+     * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     is: (input: T) => string | null;
   }
+  /**
+   * Serializer generated from `typia.json.assertStringify`.
+   *
+   * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the serialized text or throws the `TypeGuardError` of typia, which becomes a 500 `InternalServerErrorException` with the path, reason, expected type, and value.
+   * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+   * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+   */
   export interface IAssert<T> {
     type: "assert";
+    /**
+     * The generated function of the variant, taking the response data.
+     *
+     * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the serialized text or throws.
+     * @evidence contracts/common.md#clear-and-simple-design One function member.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+     * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     assert: (input: T) => string;
   }
+  /**
+   * Serializer generated from `typia.json.validateStringify`.
+   *
+   * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the `IValidation` of the text; a failure becomes a 500 `InternalServerErrorException` carrying every error.
+   * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+   * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+   */
   export interface IValidate<T> {
     type: "validate";
+    /**
+     * The generated function of the variant, taking the response data.
+     *
+     * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the validation result.
+     * @evidence contracts/common.md#clear-and-simple-design One function member.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+     * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     validate: (input: T) => IValidation<string>;
   }
+  /**
+   * Serializer generated from `typia.json.validateStringify`, for the
+   * `validate.log` mode.
+   *
+   * @evidence contracts/common.md#principled-implementation The variant tags the same function shape as `validate`, but a failure is passed to the logger registered with `TypedRoute.setValidateErrorLogger` and the response is `JSON.stringify` of the data, so a validation failure never changes the status.
+   * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+   * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+   */
   export interface IValidateLog<T> {
     type: "validate.log";
+    /**
+     * The generated function of the variant, taking the response data.
+     *
+     * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the validation result.
+     * @evidence contracts/common.md#clear-and-simple-design One function member.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+     * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     validate: (input: T) => IValidation<string>;
   }
 }

package/src/typings/Creator.ts

@@ -1,3 +1,13 @@
+/**
+ * A class constructor: anything that can be called with `new` to build an
+ * instance of `T`.
+ *
+ * @evidence contracts/common.md#principled-implementation The construct signature with rest arguments is the standard TypeScript spelling of a class type.
+ * @evidence contracts/common.md#clear-and-simple-design One construct signature.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+ * @evidence contracts/common.md#meaningful-documentation The comment states what the type stands for.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The construct signature represents JavaScript class construction rather than a native resource boundary.
+ */
 export type Creator<T extends object> = {
   new (...args: any[]): T;
 };

package/src/utils/ArrayUtil.ts

@@ -1,7 +1,26 @@
+/**
+ * Array helpers of the core runtime.
+ *
+ * @evidence contracts/common.md#principled-implementation The namespace holds the one membership helper the adapters use.
+ * @evidence contracts/common.md#clear-and-simple-design One function.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a plain helper with no special cases.
+ * @evidence contracts/common.md#meaningful-documentation The comment states its purpose.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation Array membership uses JavaScript SameValueZero comparisons with no native filesystem or process access.
+ */
 export namespace ArrayUtil {
+  /**
+   * Reports whether the array contains every one of the items.
+   *
+   * Membership is decided by `Array.prototype.includes`, so an item that is
+   * `undefined` or `NaN` is found when the array holds it.
+   *
+   * @evidence contracts/common.md#principled-implementation `Array.prototype.includes` compares by SameValueZero, so the result is the conjunction over the items of membership, an item that is `undefined` or `NaN` is found when the array holds it, and no items yields true; an earlier `find` compared the found element with `undefined` and could not report an `undefined` member.
+   * @evidence contracts/common.md#clear-and-simple-design One `every` over `includes`.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts No item is special-cased.
+   * @evidence contracts/common.md#meaningful-documentation The comment states the conjunction and the comparison rule.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Array membership uses JavaScript SameValueZero comparisons with no native filesystem or process access.
+   */
   export function has<T>(array: T[], ...items: T[]): boolean {
-    return items.every(
-      (elem) => array.find((org) => org === elem) !== undefined,
-    );
+    return items.every((item) => array.includes(item));
   }
 }

package/src/utils/ExceptionManager.ts

@@ -14,21 +14,25 @@ import { Creator } from "../typings/Creator";
  * {@link EncryptedRoute} instead of the basic router decorator functions like
  * {@link nest.Get} or {@link nest.Post} and the API function throws a custom
  * error whose class has been {@link ExceptionManager.insert inserted} in this
- * `EntityManager`, the error would be automatically converted to the regular
+ * `ExceptionManager`, the error would be automatically converted to the regular
  * {@link nest.HttpException} instance by the {@link ExceptionManager.Closure}
  * function.
  *
  * Therefore, with this `ExceptionManager` and {@link TypedRoute} or
  * {@link EncryptedRoute}, you can manage your custom error classes much
- * systemtically. You can avoid 500 internal server error or hard coding
+ * systematically. You can avoid 500 internal server error or hard coding
  * implementation about the custom error classes.
  *
- * Below error classes are defaultly configured in this `ExceptionManager`
+ * Below error class is configured in this `ExceptionManager` by default.
  *
- * - `typia.TypeGuardError`
  * - `@nestia/fetcher.HttpError`
  *
  * @author Jeongho Nam - https://github.com/samchon
+ * @evidence contracts/common.md#principled-implementation Converters are kept as an ordered list of class and closure, and an error is converted by the first class it is an instance of; the insertion keeps every subclass before its superclasses so the most specific converter wins, and `HttpError` from the fetcher is registered by default.
+ * @evidence contracts/common.md#clear-and-simple-design One namespace with the two collections and four operations; the listener set and the tuple list are the only state.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts The registration is public and explicit; no error class is special-cased except the default `HttpError` conversion.
+ * @evidence contracts/common.md#meaningful-documentation The comment documents the converter and listener concepts with an example.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation Converter ordering and listener registration operate on JavaScript class and function identity, not native path or process identity.
  */
 export namespace ExceptionManager {
   /**
@@ -39,6 +43,11 @@ export namespace ExceptionManager {
    *
    * @param creator Target error class
    * @param closure A closure function converting to the `HttpException` class
+   * @evidence contracts/common.md#principled-implementation An existing entry for the same class is removed first, then the new entry is placed before the first registered class that it extends, so specificity order holds however the calls are ordered.
+   * @evidence contracts/common.md#clear-and-simple-design One function over one list.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts The order rule is derived from the prototype chain, not from a list of known classes.
+   * @evidence contracts/common.md#meaningful-documentation The comment states the replacement and ordering rules.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Converter ordering and listener registration operate on JavaScript class and function identity, not native path or process identity.
    */
   export function insert<T extends Error>(
     creator: Creator<T>,
@@ -47,8 +56,13 @@ export namespace ExceptionManager {
     const index: number = tuples.findIndex((tuple) => tuple[0] === creator);
     if (index !== -1) tuples.splice(index, 1);
 
-    tuples.push([creator, closure]);
-    tuples.sort(([x], [y]) => (x.prototype instanceof y ? -1 : 1));
+    // an error converts by the first class it is an instance of, so a class
+    // must precede every superclass of it: insert before the first one
+    const ancestor: number = tuples.findIndex(
+      ([registered]) => creator.prototype instanceof registered,
+    );
+    if (ancestor === -1) tuples.push([creator, closure]);
+    else tuples.splice(ancestor, 0, [creator, closure]);
   }
 
   /**
@@ -56,6 +70,11 @@ export namespace ExceptionManager {
    *
    * @param creator Target error class
    * @returns Whether be erased or not
+   * @evidence contracts/common.md#principled-implementation The entry for the class is found by identity and removed, and the result says whether anything was removed.
+   * @evidence contracts/common.md#clear-and-simple-design One search and one removal.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It removes only the named class's entry.
+   * @evidence contracts/common.md#meaningful-documentation The comment states the parameter and the boolean result.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Converter ordering and listener registration operate on JavaScript class and function identity, not native path or process identity.
    */
   export function erase<T extends Error>(creator: Creator<T>): boolean {
     const index: number = tuples.findIndex((tuple) => tuple[0] === creator);
@@ -65,10 +84,29 @@ export namespace ExceptionManager {
     return true;
   }
 
+  /**
+   * Registers a listener called with every error thrown by a typed route, after
+   * the response conversion.
+   *
+   * @evidence contracts/common.md#principled-implementation The listener is added to a set, so the same function registered twice is called once.
+   * @evidence contracts/common.md#clear-and-simple-design One set insertion.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts The listener only observes; the route notifies it after the current turn and ignores its errors.
+   * @evidence contracts/common.md#meaningful-documentation The comment states when listeners are called.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Converter ordering and listener registration operate on JavaScript class and function identity, not native path or process identity.
+   */
   export function on(closure: (error: any) => any): void {
     listeners.add(closure);
   }
 
+  /**
+   * Unregisters a listener added with {@link on}.
+   *
+   * @evidence contracts/common.md#principled-implementation The listener is removed from the set by identity.
+   * @evidence contracts/common.md#clear-and-simple-design One set deletion.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It removes only the named listener.
+   * @evidence contracts/common.md#meaningful-documentation The comment names the counterpart operation.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Converter ordering and listener registration operate on JavaScript class and function identity, not native path or process identity.
+   */
   export function off(closure: (error: any) => any): void {
     listeners.delete(closure);
   }
@@ -81,6 +119,12 @@ export namespace ExceptionManager {
    * from custom error to the regular {@link nest.HttpException} instance. It
    * would be used in the {@link ExceptionManager} with {@link TypedRoute} or
    * {@link EncryptedRoute}.
+   *
+   * @evidence contracts/common.md#principled-implementation A converter is a function from the caught error to an `HttpException`, whose status and body become the response.
+   * @evidence contracts/common.md#clear-and-simple-design One call signature.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+   * @evidence contracts/common.md#meaningful-documentation The comment documents the parameter and the return value.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Converter ordering and listener registration operate on JavaScript class and function identity, not native path or process identity.
    */
   export interface Closure<T extends Error> {
     /**

package/src/utils/SourceFinder.ts

@@ -2,26 +2,53 @@ import fs from "fs";
 import { glob } from "glob";
 import path from "path";
 
+/**
+ * Finds source files by path, directory, or glob.
+ *
+ * @evidence contracts/common.md#principled-implementation The finder resolves each pattern to existing files or directories, walks directories, applies the caller's filter to files only, and subtracts the excluded set, so the result is the included files minus the excluded ones.
+ * @evidence contracts/common.md#clear-and-simple-design One public function and private walkers; the caller supplies the filter.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It contains no file names; extensions come from the caller's filter.
+ * @evidence contracts/common.md#meaningful-documentation The comment states its purpose.
+ * @evidence contracts/portability.md#os-neutral-implementation The finder turns each pattern into an absolute native path with `path.resolve` and asks the filesystem itself, through `existsSync`, `stat` and `readdir`, whether a path exists and what it is, so the volume's own case policy and links apply. Only the part of a pattern below its longest existing ancestor is globbed, rewritten from the native separator to `/` because glob reads a Windows backslash as an escape. Remaining assumptions: the case policy of wildcard matching is glob's own platform default and not a probe of the volume, accepted files are keyed by filesystem real path while returned locations retain their discovered spelling, and directory links are followed once per real path in each include or exclude collection, so aliases and cycles do not repeat a traversal.
+ */
 export namespace SourceFinder {
+  /**
+   * Returns the files matched by the include patterns and not by the exclude
+   * patterns.
+   *
+   * A pattern may name a file, a directory that is walked recursively, or a
+   * glob. Only files accepted by the filter are returned.
+   *
+   * @evidence contracts/common.md#principled-implementation A pattern that exists on disk is used as a path; otherwise its longest existing ancestor becomes the base of a glob search, so a pattern with wildcards is matched below the part of the path that exists, and a base that does not exist matches nothing; accepted file identities use filesystem real paths, so includes and exclusions agree across links and case aliases while output retains a discovered native spelling.
+   * @evidence contracts/common.md#clear-and-simple-design One function that runs the same collection twice, once adding and once removing.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts The result follows the patterns and the filter, with no fixed directory.
+   * @evidence contracts/common.md#meaningful-documentation The comment states the pattern forms and the filtering.
+   * @evidence contracts/portability.md#os-neutral-implementation An existing path is used literally, so no character glob reads specially is interpreted. Otherwise the nearest existing ancestor, found with `existsSync` and `dirname` until the filesystem root, is the glob's working directory and the matches are resolved against it, so a drive letter or a UNC root never enters the pattern.
+   */
   export const find = async (props: IProps): Promise<string[]> => {
-    const dict: Set<string> = new Set();
+    const dict: Map<string, string> = new Map();
 
-    await emplace(props.filter)(props.include)((str) => dict.add(str));
+    await emplace(props.filter)(props.include)((str) =>
+      dict.set(fs.realpathSync.native(str), str),
+    );
     if (props.exclude?.length)
-      await emplace(props.filter)(props.exclude)((str) => dict.delete(str));
+      await emplace(props.filter)(props.exclude)((str) =>
+        dict.delete(fs.realpathSync.native(str)),
+      );
 
-    return [...dict];
+    return [...dict.values()];
   };
 
   const emplace =
     (filter: (file: string) => boolean) =>
     (input: string[]) =>
     async (closure: (location: string) => void): Promise<void> => {
+      const visited: Set<string> = new Set();
       for (const pattern of input) {
-        for (const file of await _Glob(path.resolve(pattern))) {
+        for (const file of await _Glob(pattern)) {
           const stats: fs.Stats = await fs.promises.stat(file);
           if (stats.isDirectory() === true)
-            await iterate(filter)(closure)(file);
+            await iterate(filter)(closure)(file, visited);
           else if (stats.isFile() && filter(file)) closure(file);
         }
       }
@@ -30,20 +57,45 @@ export namespace SourceFinder {
   const iterate =
     (filter: (location: string) => boolean) =>
     (closure: (location: string) => void) =>
-    async (location: string): Promise<void> => {
+    async (location: string, visited: Set<string>): Promise<void> => {
+      const identity: string = await fs.promises.realpath(location);
+      if (visited.has(identity)) return;
+      visited.add(identity);
       const directory: string[] = await fs.promises.readdir(location);
       for (const file of directory) {
         const next: string = path.resolve(`${location}/${file}`);
         const stats: fs.Stats = await fs.promises.stat(next);
 
-        if (stats.isDirectory() === true) await iterate(filter)(closure)(next);
+        if (stats.isDirectory() === true)
+          await iterate(filter)(closure)(next, visited);
         else if (stats.isFile() && filter(next)) closure(next);
       }
     };
 
+  /**
+   * Files and directories a path or glob pattern names.
+   *
+   * An existing path is taken literally, whatever characters it holds, as a
+   * directory such as `app [v2]` would otherwise read as a character class. For
+   * a pattern, the longest existing ancestor is the literal base and only the
+   * rest is globbed, with `/` separators, since glob reads a Windows backslash
+   * as an escape.
+   */
   const _Glob = async (pattern: string): Promise<string[]> => {
-    const matches = await glob(pattern);
-    return matches.map((str) => path.resolve(str));
+    const absolute: string = path.resolve(pattern);
+    if (fs.existsSync(absolute)) return [absolute];
+    let base: string = absolute;
+    while (fs.existsSync(base) === false) {
+      const parent: string = path.dirname(base);
+      if (parent === base) return [];
+      base = parent;
+    }
+    const rest: string = path
+      .relative(base, absolute)
+      .split(path.sep)
+      .join("/");
+    const matches: string[] = await glob(rest, { cwd: base });
+    return matches.map((str) => path.resolve(base, str));
   };
 }
 

package/src/utils/VersioningStrategy.ts

@@ -1,27 +1,71 @@
 import { VERSION_NEUTRAL, VersionValue } from "@nestjs/common/interfaces";
 
+/**
+ * Resolves the URI versions of a controller method the way NestJS does.
+ *
+ * @evidence contracts/common.md#principled-implementation The namespace turns the version metadata of a controller and a method, with the default version of the application, into the version path segments, following NestJS's precedence.
+ * @evidence contracts/common.md#clear-and-simple-design Two functions and one configuration type.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts The precedence follows NestJS; no version string is special-cased.
+ * @evidence contracts/common.md#meaningful-documentation The comment states its purpose.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation Version precedence and prefix concatenation produce HTTP URI segments and never resolve native filesystem paths.
+ */
 export namespace VersioningStrategy {
+  /**
+   * The URI versioning options the adapter reads: the prefix and the default
+   * version.
+   *
+   * @evidence contracts/common.md#principled-implementation The two fields are what NestJS's URI versioning uses to build a version segment.
+   * @evidence contracts/common.md#clear-and-simple-design A two-field record.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+   * @evidence contracts/common.md#meaningful-documentation The comment names the two fields.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Version precedence and prefix concatenation produce HTTP URI segments and never resolve native filesystem paths.
+   */
   export interface IConfig {
     prefix: string;
     defaultVersion?: VersionValue;
   }
 
+  /**
+   * Casts version metadata to a list: a missing value stays absent and a single
+   * value is a one-element list.
+   *
+   * @evidence contracts/common.md#principled-implementation One version becomes a list while absence and an explicit empty list remain distinct, because Nest treats an empty version list as no registered paths rather than inherited versions.
+   * @evidence contracts/common.md#clear-and-simple-design One conditional expression.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts It adds nothing to the values.
+   * @evidence contracts/common.md#meaningful-documentation The comment states the three cases.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Version precedence and prefix concatenation produce HTTP URI segments and never resolve native filesystem paths.
+   */
   export const cast = (
     value: VersionValue | undefined,
-  ): Array<string | typeof VERSION_NEUTRAL> =>
-    value === undefined ? [] : Array.isArray(value) ? value : [value];
+  ): Array<string | typeof VERSION_NEUTRAL> | undefined =>
+    value === undefined ? undefined : Array.isArray(value) ? value : [value];
 
+  /**
+   * Version path segments of a route, resolved as NestJS resolves them: the
+   * method's versions, else the controller's, else the default version, and no
+   * version at all is the unversioned path (#1735).
+   *
+   * @evidence contracts/common.md#principled-implementation The first present method, controller or default version list wins, including an empty list that registers no paths. Duplicates are dropped, a neutral version maps to no segment, and absent metadata also maps to no segment; with versioning off the only path has no version.
+   * @evidence contracts/common.md#clear-and-simple-design One function returning the segments, curried on the configuration so a caller can compute the segments per method.
+   * @evidence contracts/common.md#prohibited-implementation-shortcuts The precedence is NestJS's, and no version is special-cased.
+   * @evidence contracts/common.md#meaningful-documentation The comment states the precedence and the neutral version rule.
+   * @evidenceExclude contracts/portability.md#os-neutral-implementation Version precedence and prefix concatenation produce HTTP URI segments and never resolve native filesystem paths.
+   */
   export const merge =
     (config: IConfig | undefined) =>
-    (values: Array<string | typeof VERSION_NEUTRAL>): string[] => {
+    (props: {
+      controller: Array<string | typeof VERSION_NEUTRAL> | undefined;
+      method: Array<string | typeof VERSION_NEUTRAL> | undefined;
+    }): string[] => {
       if (config === undefined) return [""];
-      const set: Set<string | typeof VERSION_NEUTRAL> = new Set(values);
-      const array: Array<string | typeof VERSION_NEUTRAL> =
-        set.size === 0 ? cast(config.defaultVersion) : Array.from(set);
-      return !!array?.length
-        ? array.map((x) =>
-            typeof x === "symbol" ? "" : `${config.prefix}${x}`,
-          )
-        : [];
+      const chosen: Array<string | typeof VERSION_NEUTRAL> | undefined =
+        props.method ?? props.controller ?? cast(config.defaultVersion);
+      if (chosen === undefined) return [""];
+      const unique: Array<string | typeof VERSION_NEUTRAL> = [
+        ...new Set(chosen),
+      ];
+      return unique.map((x) =>
+        typeof x === "symbol" ? "" : `${config.prefix}${x}`,
+      );
     };
 }

package/lib/transform.d.ts

@@ -1,10 +0,0 @@
-import type { ITtscPlugin, ITtscPluginFactoryContext } from "ttsc";
-/**
- * `@nestia/core` ttsc plugin descriptor.
- *
- * `@nestia/sdk` is not a standalone plugin: its Go transform is declared here
- * as a `contributor` that ttsc statically links into this host binary, and only
- * when `@nestia/sdk` is actually resolvable from the project. A project
- * depending on `@nestia/core` alone never compiles any SDK transform code.
- */
-export default function createTtscPlugin(context: ITtscPluginFactoryContext): ITtscPlugin;

package/lib/transform.js

@@ -1,25 +0,0 @@
-"use strict";
-var __importDefault = (this && this.__importDefault) || function (mod) {
-    return (mod && mod.__esModule) ? mod : { "default": mod };
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.default = createTtscPlugin;
-const node_module_1 = require("node:module");
-const node_path_1 = __importDefault(require("node:path"));
-/**
- * `@nestia/core` ttsc plugin descriptor.
- *
- * `@nestia/sdk` is not a standalone plugin: its Go transform is declared here
- * as a `contributor` that ttsc statically links into this host binary, and only
- * when `@nestia/sdk` is actually resolvable from the project. A project
- * depending on `@nestia/core` alone never compiles any SDK transform code.
- */
-function createTtscPlugin(context) {
-    const requireFrom = (0, node_module_1.createRequire)(node_path_1.default.join(context.projectRoot, "package.json"));
-    const root = node_path_1.default.dirname(requireFrom.resolve("@nestia/core/package.json"));
-    return {
-        name: "@nestia/core",
-        source: node_path_1.default.resolve(root, "native", "cmd", "ttsc-nestia"),
-    };
-}
-//# sourceMappingURL=transform.js.map

package/lib/transform.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"transform.js","sourceRoot":"","sources":["../src/transform.ts"],"names":[],"mappings":";;;;;;AAAA,6CAA4C;AAC5C,0DAA6B;AAG7B;;;;;;;GAOG;AACH,0BACE,OAAkC;IAElC,MAAM,WAAW,GAAG,IAAA,2BAAa,EAC/B,mBAAI,CAAC,IAAI,CAAC,OAAO,CAAC,WAAW,EAAE,cAAc,CAAC,CAC/C,CAAC;IACF,MAAM,IAAI,GAAW,mBAAI,CAAC,OAAO,CAC/B,WAAW,CAAC,OAAO,CAAC,2BAA2B,CAAC,CACjD,CAAC;IACF,OAAO;QACL,IAAI,EAAE,cAAc;QACpB,MAAM,EAAE,mBAAI,CAAC,OAAO,CAAC,IAAI,EAAE,QAAQ,EAAE,KAAK,EAAE,aAAa,CAAC;KAC3D,CAAC;AACJ,CAAC"}

package/src/transform.ts

@@ -1,26 +0,0 @@
-import { createRequire } from "node:module";
-import path from "node:path";
-import type { ITtscPlugin, ITtscPluginFactoryContext } from "ttsc";
-
-/**
- * `@nestia/core` ttsc plugin descriptor.
- *
- * `@nestia/sdk` is not a standalone plugin: its Go transform is declared here
- * as a `contributor` that ttsc statically links into this host binary, and only
- * when `@nestia/sdk` is actually resolvable from the project. A project
- * depending on `@nestia/core` alone never compiles any SDK transform code.
- */
-export default function createTtscPlugin(
-  context: ITtscPluginFactoryContext,
-): ITtscPlugin {
-  const requireFrom = createRequire(
-    path.join(context.projectRoot, "package.json"),
-  );
-  const root: string = path.dirname(
-    requireFrom.resolve("@nestia/core/package.json"),
-  );
-  return {
-    name: "@nestia/core",
-    source: path.resolve(root, "native", "cmd", "ttsc-nestia"),
-  };
-}