@akanjs/cli 0.0.55 → 0.0.57

package/index.js

@@ -326,21 +326,6 @@ var import_dayjs3 = __toESM(require("dayjs"));
 var import_customParseFormat = __toESM(require("dayjs/plugin/customParseFormat"));
 import_dayjs3.default.extend(import_customParseFormat.default);
 
-// pkgs/@akanjs/common/randomPicks.ts
-var randomPicks = (arr, count = 1, allowDuplicate = false) => {
-  if (!allowDuplicate && arr.length <= count)
-    return arr;
-  const idxs = [];
-  let pickIdx;
-  for (let i = 0; i < count; i++) {
-    do {
-      pickIdx = Math.floor(Math.random() * arr.length);
-    } while (!allowDuplicate && idxs.includes(pickIdx));
-    idxs.push(pickIdx);
-  }
-  return idxs.map((idx) => arr[idx]);
-};
-
 // pkgs/@akanjs/common/pluralize.ts
 var import_pluralize = __toESM(require("pluralize"));
 
@@ -2490,540 +2475,6 @@ dictionaryStart
 
 dictionaryEnd
 
-`;
-var frameworkAbstract = `
-Intro
-- Build an all-stack application at once.
-- Write one line, deploy on web, app, server, database, and infra.
-- Akan is a framework with least code, highest performance for typescript-written applications.
-
-Key features
-- Integral interface: Akan serves an interface for building from schema, to service logic, api endpoint, state management, and component design.
-- Stable, Scalable, Safe built-in architecture: Fully type-safe, i18n, security, file management, text-search, automatic documentation, admin page, etc are all served with modular development.
-- application as a service: Akan deploys server, database, web, app at once through Akan cloud. Commit once, deploy and manage all.
-
-Procedure
-- add field on database and api at once, with fully typed
-- add backend api endpoint and frontend fetch function at once, with fully typed
-- write query interface and use everywhere!
-- No spaghetti state management anymore, build your global store with domain-driven state&actions.
-- No Spaghetti Components anymore, build your page with domain-driven components
-- write one page, use SSR on Next.js and build Android&iOS CSR app with beautiful page transitions!
-- built-in ai code generation, tell about business, the logic is generated.
-`;
-var scalarConstantDescription = `
-Purpose and Structure
-
-Scalar constant files define reusable data structures that can be embedded within other models. They represent complex field types
-that are not entities themselves but are used as components within larger data models. These are located in the __scalar directory
-within application or library modules.
-
-Key Characteristics
-
-- Defined with @Model.Scalar decorator (not @Model.Input, @Model.Object, etc.)
-- Do not have their own database collection
-- Cannot be queried independently
-- Used as embedded objects within other models
-- Often represent complex value objects or domain concepts
-
-Creating Scalar Constant Files
-
-File Organization
-
-1. Place scalar constants in the lib/__scalar/{scalarName}/ directory
-2. Name the file {scalarName}.constant.ts
-3. Register scalars in the _server.ts file in the __scalar directory
-
-Basic Structure
-
-import { Field, Model } from "@akanjs/constant";
-import { enumOf, Int, Dayjs } from "@akanjs/base"; // Import needed types
-
-// Optional: Define enums used by this scalar
-export const ScalarEnum = enumOf(["value1", "value2", "value3"] as const);
-export type ScalarEnum = enumOf<typeof ScalarEnum>;
-
-@Model.Scalar("ScalarName")  // Use the @Model.Scalar decorator
-export class ScalarName {
-  // Define properties with @Field.Prop decorator
-  @Field.Prop(() => String)
-  stringProperty: string;
-
-  @Field.Prop(() => Int, { min: 0 })
-  numericProperty: number;
-
-  @Field.Prop(() => Boolean, { default: false })
-  booleanProperty: boolean;
-
-  @Field.Prop(() => Date)
-  dateProperty: Dayjs;
-
-  @Field.Prop(() => String, { enum: ScalarEnum })
-  enumProperty: ScalarEnum;
-
-  @Field.Prop(() => String, { nullable: true })
-  optionalProperty: string | null;
-}
-
-
-Common Types of Scalar Objects
-
-Based on the analyzed codebase, here are common patterns for scalar objects:
-
-1. Value Objects
-
-Simple structures that group related properties:
-
-@Model.Scalar("Address")
-export class Address {
-  @Field.Prop(() => String)
-  street: string;
-
-  @Field.Prop(() => String)
-  city: string;
-
-  @Field.Prop(() => String)
-  zipCode: string;
-
-  @Field.Prop(() => String)
-  country: string;
-}
-
-2. Configuration Objects
-
-Objects holding configuration or settings:
-
-@Model.Scalar("NotificationSettings")
-export class NotificationSettings {
-  @Field.Prop(() => Boolean, { default: true })
-  emailEnabled: boolean;
-
-  @Field.Prop(() => Boolean, { default: true })
-  pushEnabled: boolean;
-
-  @Field.Prop(() => Boolean, { default: false })
-  smsEnabled: boolean;
-}
-
-3. Metadata Objects
-
-Objects providing metadata about other entities:
-
-@Model.Scalar("FileMeta")
-export class FileMeta {
-  @Field.Prop(() => Date)
-  lastModifiedAt: Dayjs;
-
-  @Field.Prop(() => Int)
-  size: number;
-
-  @Field.Prop(() => String, { nullable: true })
-  mimeType: string | null;
-}
-
-4. Complex Value Type Objects
-
-Objects representing domain-specific complex values:
-
-@Model.Scalar("GeoLocation")
-export class GeoLocation {
-  @Field.Prop(() => Float)
-  latitude: number;
-
-  @Field.Prop(() => Float)
-  longitude: number;
-
-  @Field.Prop(() => Float, { nullable: true })
-  altitude: number | null;
-}
-
-Best Practices
-
-1. Keep it Simple: Scalar objects should be focused on a single concept
-2. No External References: Avoid referencing entities directly from scalar objects
-3. Validation Rules: Include validation rules in field definitions
-4. Default Values: Provide sensible defaults where appropriate
-5. Documentation: Document the purpose and usage of each scalar type
-6. Reusability: Design scalar objects to be reusable across different models
-7. Immutability: Treat scalar objects as immutable value objects
-8. Naming Convention: Use descriptive names that reflect the domain concept
-
-Using Scalar Types in Models
-
-After defining scalar objects, you can use them in your entity models:
-
-import { Field, Model } from "@akanjs/constant";
-import { FileMeta } from "../__scalar/fileMeta/fileMeta.constant";
-import { ExternalLink } from "../__scalar/externalLink/externalLink.constant";
-
-@Model.Input("ProfileInput")
-export class ProfileInput {
-  @Field.Prop(() => String)
-  name: string;
-
-  @Field.Prop(() => FileMeta, { nullable: true })
-  avatar: FileMeta | null;
-
-  @Field.Prop(() => [ExternalLink])
-  socialLinks: ExternalLink[];
-}
-
-Key Differences from Regular Models
-
-This structured approach to scalar objects helps maintain clean, modular, and reusable code across your application, while keeping
-the domain concepts well-organized and type-safe.
-`;
-var howToSetFieldInModelConstant = `
-Comprehensive Guide to @Field Decorators in constant.ts Files
-
-The @Field decorator is a crucial component for defining schema fields in your constant.ts files. This guide provides detailed
-information about using @Field.Prop and @Field.Secret decorators with various types and option configurations.
-
-Basic Structure
-
-@Field.Prop(() => TypeFunction, optionsObject)
-fieldName: FieldType;
-
-Field Decorator Types
-
-1. @Field.Prop
-
-The standard field decorator used for most properties in your models.
-
-@Field.Prop(() => String)
-name: string;
-
-2. @Field.Secret
-
-Used for sensitive data that should be handled with extra security measures. These fields are typically excluded from normal queries
-and responses by default.
-
-@Field.Secret(() => String)
-password: string;
-
-Data Type Functions
-
-The first argument to a field decorator is a type function that defines the data type:
-
-Basic Types
-
-@Field.Prop(() => String)
-name: string;
-
-@Field.Prop(() => Int)
-age: number;
-
-@Field.Prop(() => Float)
-weight: number;
-
-@Field.Prop(() => Boolean)
-isActive: boolean;
-
-@Field.Prop(() => Date)
-createdAt: Dayjs;
-
-@Field.Prop(() => ID)
-userId: string;
-
-@Field.Prop(() => JSON)
-metadata: any;
-
-Array Types
-
-@Field.Prop(() => [String])
-tags: string[];
-
-@Field.Prop(() => [Int])
-scores: number[];
-
-@Field.Prop(() => [UserModel])
-friends: UserModel[];
-
-Reference Types
-
-// Reference to scalar types
-@Field.Prop(() => FileMeta)
-fileMeta: FileMeta;
-
-// Reference to entity models
-@Field.Prop(() => LightUser)
-user: LightUser;
-
-Enum Types
-
-@Field.Prop(() => String, { enum: UserStatus })
-status: UserStatus;
-
-@Field.Prop(() => [String], { enum: UserRole })
-roles: UserRole[];
-
-Field Options
-
-The second argument to field decorators is an options object that can include many configuration settings:
-
-Nullability
-
-// Non-nullable field (default)
-@Field.Prop(() => String)
-requiredField: string;
-
-// Nullable field
-@Field.Prop(() => String, { nullable: true })
-optionalField: string | null;
-
-Default Values
-
-// Static default value
-@Field.Prop(() => String, { default: "Untitled" })
-title: string;
-
-// Dynamic default value (function)
-@Field.Prop(() => Date, { default: () => dayjs() })
-createdAt: Dayjs;
-
-// Default for arrays
-@Field.Prop(() => [Int], { default: [0, 0] })
-coordinates: number[];
-
-// Default for objects
-@Field.Prop(() => JSON, { default: {} })
-settings: Record<string, any>;
-
-Validation Constraints
-
-// String length
-@Field.Prop(() => String, { min: 3, max: 100 })
-name: string;
-
-// Numeric range
-@Field.Prop(() => Int, { min: 0, max: 100 })
-score: number;
-
-// Custom type validation
-@Field.Prop(() => String, { type: "email" })
-email: string;
-
-@Field.Prop(() => String, { type: "url" })
-website: string;
-
-@Field.Prop(() => String, { type: "phone" })
-phone: string;
-
-// Multiple constraints
-@Field.Prop(() => String, {
-  min: 8,
-  max: 50,
-  regex: /^[a-zA-Z0-9!@#$%^&*()]+$/
-})
-password: string;
-
-Enumerations
-
-// Single enum value
-@Field.Prop(() => String, { enum: UserRole, default: "user" })
-role: UserRole;
-
-// Array of enum values
-@Field.Prop(() => [String], { enum: Permissions, default: ["read"] })
-permissions: Permissions[];
-
-// Multiple enum constraints
-@Field.Prop(() => [String], [{ enum: Verify }])
-verifies: Verify[];
-
-Database-Specific Options
-
-// Unique constraint
-@Field.Prop(() => String, { unique: true })
-username: string;
-
-// Index field
-@Field.Prop(() => String, { index: true })
-category: string;
-
-// Case-insensitive index
-@Field.Prop(() => String, { index: { collation: { locale: "en", strength: 2 } } })
-searchTerm: string;
-
-Accumulation for Insights
-
-Used specifically in Insight models to define how to aggregate data:
-
-@Field.Prop(() => Int, { default: 0, accumulate: { $sum: 1 } })
-count: number;
-
-@Field.Prop(() => Int, { default: 0, accumulate: { $sum: "$amount" } })
-totalAmount: number;
-
-@Field.Prop(() => Int, { accumulate: { $avg: "$score" } })
-averageScore: number;
-
-@Field.Prop(() => Int, { accumulate: { $max: "$value" } })
-highestValue: number;
-
-Query Options for Summary Models
-
-Used specifically in Summary models to define query criteria for aggregate calculations:
-
-// Basic query - count all records
-@Field.Prop(() => Int, { min: 0, default: 0, query: {} })
-totalRecords: number;
-
-// Filtered query - count records with specific status
-@Field.Prop(() => Int, { min: 0, default: 0, query: { status: "active" } })
-activeRecords: number;
-
-// Complex query - count records matching multiple criteria
-@Field.Prop(() => Int, { query: { status: "active", type: "premium" } })
-activePremiumUsers: number;
-
-// Dynamic query using a function
-@Field.Prop(() => Int, {
-  query: () => ({ lastLoginAt: { $gte: dayjs().subtract(1, "day").toDate() } })
-})
-dailyActiveUsers: number;
-
-// Combined constraints
-@Field.Prop(() => Int, {
-  min: 0,
-  default: 0,
-  query: { status: { $ne: "deleted" } }
-})
-nonDeletedRecords: number;
-
-Reference Options
-
-// Basic reference
-@Field.Prop(() => OtherModel)
-relatedItem: OtherModel;
-
-// Reference with rendering option for UI
-@Filter.Arg("userId", () => ID, {
-  ref: "user",
-  renderOption: (user: LightUser) => user.nickname
-})
-userId: string;
-
-Combined Examples
-
-Complex Object Reference with Nullable
-
-@Field.Prop(() => UserProfile, { nullable: true })
-profile: UserProfile | null;
-
-Array of References with Default
-
-@Field.Prop(() => [File], { default: [] })
-attachments: File[];
-
-Enum with Default and Validation
-
-@Field.Prop(() => String, {
-  enum: StatusType,
-  default: "pending",
-  validate: (value) => ["pending", "active", "completed"].includes(value)
-})
-status: StatusType;
-
-Dynamic Default with Constraints
-
-@Field.Prop(() => Date, {
-  default: () => dayjs().add(7, "days"),
-  validate: (date) => date > dayjs().toDate()
-})
-expiresAt: Dayjs;
-
-Special Use Cases
-
-Computed Fields
-
-@Field.Prop(() => Int, { compute: (doc) => doc.items.reduce((sum, item) => sum + item.price, 0) })
-totalPrice: number;
-
-Virtual Fields (not stored in database)
-
-@Field.Prop(() => String, { virtual: true })
-get fullName(): string {
-  return \`\${this.firstName} \${this.lastName}\`;
-}
-
-Combined Validators
-
-@Field.Prop(() => String, {
-  validators: [
-    { validator: (v) => v.length >= 8, message: "Password must be at least 8 characters" },
-    { validator: (v) => /[A-Z]/.test(v), message: "Password must contain uppercase letter" },
-    { validator: (v) => /[0-9]/.test(v), message: "Password must contain a number" }
-  ]
-})
-password: string;
-
-Custom Field Types with Formatting
-
-@Field.Prop(() => String, {
-  type: "phone",
-  format: (value) => value.replace(/(d{3})(d{4})(d{4})/, "$1-$2-$3")
-})
-phone: string;
-
-Best Practices for Field Decorators
-
-1. Be Explicit with Types: Always specify the correct type function that matches the TypeScript type.
-2. Set Appropriate Defaults: Provide sensible default values for fields that might be omitted during creation.
-3. Use Nullability Correctly: Only mark fields as nullable if they can legitimately be null in your domain model.
-4. Add Validation Constraints: Include appropriate min/max/regex constraints to ensure data integrity.
-5. Document Special Fields: Add comments for fields with special business logic or validation requirements.
-6. Group Related Fields: Keep related fields together for better readability.
-7. Use Enums Consistently: Always use enumOf for enumerated values and reference them correctly.
-8. Limit Secrets: Only use @Field.Secret for truly sensitive data.
-9. Consistent Naming: Use clear, descriptive names for fields that reflect their domain purpose.
-10. Type References: When referencing other models, import them correctly and use their proper type.
-
-By following these guidelines and leveraging the full power of field decorators with their options, you can create robust, type-safe
-schemas that enforce your domain rules at the data layer.
-`;
-var requestScalarConstant = ({
-  sysName,
-  modelName,
-  modelDesc,
-  modelSchemaDesign,
-  boilerplate,
-  otherConstants
-}) => `
-\uB108\uB294 Akan.js\uB77C\uB294 \uC0AC\uB0B4 \uD504\uB808\uC784\uC6CC\uD06C\uB85C Typescript \uAE30\uBC18 \uD504\uB85C\uADF8\uB7A8\uC744 \uC791\uC131\uD558\uB294 \uC2DC\uB2C8\uC5B4 \uAC1C\uBC1C\uC790\uC57C.
-\uB2E4\uC74C\uC758 \uBC30\uACBD \uC815\uBCF4\uB97C \uBC14\uD0D5\uC73C\uB85C ${modelName}.constant.ts \uD30C\uC77C\uC744 \uC791\uC131\uD574\uC918.
-
-1. Akan.js \uD504\uB808\uC784\uC6CC\uD06C\uC5D0 \uB300\uD55C \uAC1C\uC694
-${frameworkAbstract}
-
-2. <model>.constant.ts \uD30C\uC77C\uC5D0 \uB300\uD55C \uAC1C\uC694
-${scalarConstantDescription}
-
-3. <model.constant.ts \uD30C\uC77C\uC758 Field \uC791\uC131\uBC95
-${howToSetFieldInModelConstant}
-
-4. \uD604\uC7AC \uD504\uB85C\uC81D\uD2B8 \uB0B4 \uB2E4\uB978 constant.ts \uD30C\uC77C\uB4E4\uC5D0 \uB300\uD55C \uC608\uC2DC
-${otherConstants.map(
-  (constant) => `
-Example file: ${constant.path}
-\`\`\`
-${constant.content}
-\`\`\`
-`
-).join("\n")}
-
-
-\uC704 \uB0B4\uC6A9\uB4E4\uC744 \uBC14\uD0D5\uC73C\uB85C \uD30C\uC2F1\uD558\uAE30 \uC27D\uAC8C \uC544\uB798\uC5D0 \uBCF4\uC77C\uB7EC\uD50C\uB808\uC774\uD2B8\uC5D0 \uB9DE\uAC8C \uC815\uB9AC\uD574\uC11C \uC918
-
-Application name: ${sysName}
-Model name: ${modelName}
-Model description: ${modelDesc}
-Model schema design: ${modelSchemaDesign}
-
-Target filename: ${modelName}.constant.ts
-\`\`\`
-${boilerplate}
-\`\`\`
 `;
 
 // pkgs/@akanjs/cli/src/application/application.prompt.ts
@@ -3213,7 +2664,7 @@ var ApplicationRunner = class {
           NEXT_PUBLIC_SERVE_DOMAIN: processEnv.NEXT_PUBLIC_SERVE_DOMAIN ?? "localhost",
           NEXT_PUBLIC_ENV: processEnv.NEXT_PUBLIC_ENV ?? "debug",
           NEXT_PUBLIC_OPERATION_MODE: processEnv.NEXT_PUBLIC_OPERATION_MODE ?? "local",
-          NEXT_PUBLIC_LOG_LEVEL: processEnv.NEXT_PUBLIC_LOG_LEVEL ?? "debug",
+          NEXT_PUBLIC_LOG_LEVEL: processEnv.NEXT_PUBLIC_LOG_LEVEL ?? "log",
           NEXT_PUBLIC_APP_NAME: app.name,
           APP_OPERATION_MODE: processEnv.APP_OPERATION_MODE ?? "local",
           AKAN_WORKSPACE_ROOT: app.workspace.workspaceRoot,
@@ -3869,12 +3320,14 @@ var PackageRunner = class {
       main: "./index.js",
       engines: { node: ">=22" },
       dependencies,
-      exports: {
-        ".": {
-          require: pkgJson.type === "module" ? "./index.cjs" : "./index.js",
-          import: pkgJson.type === "module" ? "./index.js" : "./index.mjs"
-        },
-        ...pkgJson.exports ?? {}
+      ...["@akanjs/config", "@akanjs/cli"].includes(pkg.name) ? {} : {
+        exports: {
+          ".": {
+            require: pkgJson.type === "module" ? "./index.cjs" : "./index.js",
+            import: pkgJson.type === "module" ? "./index.js" : "./index.mjs"
+          },
+          ...pkgJson.exports ?? {}
+        }
       }
     };
     if (buildResult.outputFiles)
@@ -4068,11 +3521,13 @@ CloudCommand = __decorateClass([
 
 // pkgs/@akanjs/cli/src/library/library.command.ts
 var LibraryCommand = class {
+  libraryScript = new LibraryScript();
   async createLibrary(name, workspace) {
   }
   async removeLibrary(lib, workspace) {
   }
   async scanLibrary(lib) {
+    await this.libraryScript.scanLibrary(lib);
   }
   async buildLibrary(lib) {
   }
@@ -4105,9 +3560,6 @@ LibraryCommand = __decorateClass([
   Commands()
 ], LibraryCommand);
 
-// pkgs/@akanjs/cli/src/module/module.script.ts
-var import_prompts8 = require("@inquirer/prompts");
-
 // pkgs/@akanjs/cli/src/module/module.runner.ts
 var import_output_parsers2 = require("@langchain/core/output_parsers");
 var import_prompts7 = require("@langchain/core/prompts");
@@ -4283,19 +3735,6 @@ var ModuleScript = class {
       )).flat()
     ];
     const { constant, dictionary } = await this.#runner.createScalarTemplate(sys2, name);
-    const scalarDescription = await (0, import_prompts8.input)({ message: "Enter the model scalar description" });
-    const scalarSchemaDescription = await (0, import_prompts8.input)({ message: "What fields and schema design do you want?" });
-    const scalarConstantRequest = requestScalarConstant({
-      sysName: sys2.name,
-      modelName: name,
-      modelDesc: scalarDescription,
-      modelSchemaDesign: scalarSchemaDescription,
-      boilerplate: constant.content,
-      otherConstants: randomPicks(scalarConstantExampleFiles, Math.min(10, scalarConstantExampleFiles.length))
-    });
-    const response = await streamAi(scalarConstantRequest, (chunk) => {
-      process.stdout.write(chunk);
-    });
   }
   async createService(workspace, name) {
   }

package/package.json

@@ -1,7 +1,7 @@
 {
   "type": "commonjs",
   "name": "@akanjs/cli",
-  "version": "0.0.55",
+  "version": "0.0.57",
   "bin": {
     "akan": "index.js"
   },
@@ -48,11 +48,5 @@
     "vite": "^6.3.4",
     "vite-plugin-node-polyfills": "^0.23.0",
     "vite-tsconfig-paths": "^5.1.4"
-  },
-  "exports": {
-    ".": {
-      "require": "./index.js",
-      "import": "./index.mjs"
-    }
   }
 }

package/pkgs/@akanjs/cli/src/library/library.command.d.ts

@@ -1,5 +1,7 @@
 import { Lib, Workspace } from "@akanjs/devkit";
+import { LibraryScript } from "./library.script";
 export declare class LibraryCommand {
+    libraryScript: LibraryScript;
     createLibrary(name: string, workspace: Workspace): Promise<void>;
     removeLibrary(lib: Lib, workspace: Workspace): Promise<void>;
     scanLibrary(lib: Lib): Promise<void>;