(cli): Proposal for new `agentica` CLI
We have two commands right now create-agentica and agentica , and create-agentica is an alias of agentica In my idea, can we change them like this(if you are creating tutorials, I'm sorry to this breaking change)
-
create-agenticacreate-agentica gonna be the cli tool to start the project. It transfers the functionality thatagenticacurrently has. When users start project, they execute like
pnpm create agentica
# or
pnpm create agentica --backend
pnpm create agentica --frontend
like that
-
agenticaagentica gonna be the wrapper command running with Agentica. It is like wrangler command or astro command, which are wrappers of vite/tsc or whatever. So for example, we wrap tsc or ts-node or idk more faster bundler like esbuld to create more ergonomic command
# current commands in template
ts-node ./src/index.ts # for dev
tsc # for build
# using agentica command
agentica dev # wrapper of ts-node? or rslib, esbuild whatever
agentica build # wrapper of tsc, rsbulid, rollup, esbuild, or whatever
agentica prepare # wrapper of ts-patch install
This way, users can use agentica without having to worry about typia settings or ts-patch settings. Any thought? I think Agentica is an EASY rather than SIMPLE solution, so creating an agentica command would be a DX improvement.
Also, we can re-export unplugin-typia from agentica like
import Agentica from 'agentica/vite';
import { defineConfig } from 'vite';
export defineConfig({
plugin: [Agentica()],
})
Task List:
I think it's good What do you think? @samchon
Looks good.
If possible to make the agentica dev command to work different for each environment like NestJS/NodeJS/Standalone cases, let's do it.
As our CLI commands are following @nest/cli's structure, need to investigate its source code when developing NestJS env supporting.