Scaffold web, API, full-stack, and Node CLI workspaces with npm workspaces, React (Vite), Express, shared code, and optional auth / database / logging stubs.

Requirements

• Node.js 20+
• npm (for generated projects and optional git init / npm install steps)

Install

Install the package locally (no -g). Run it with npx so npm resolves the CLI from node_modules.

npm install tejasetup

Then use tejas or tejasetup via npx (there is no npx install tejasetup — use npx tejasetup or the commands below):

npx tejasetup                    # interactive create (same as init)
npx tejasetup init
npx --package=tejasetup tejas init   # same binary, explicit name `tejas`

You can also call the binaries directly:

./node_modules/.bin/tejas init
./node_modules/.bin/tejasetup doctor

No prior install — npx can download and run a version from the registry (still not global):

npx tejasetup
npx tejasetup@latest init

Optional package.json script (shorter typing after npm install tejasetup):

{
  "scripts": {
    "new-project": "tejasetup"
  }
}

Then: npm run new-project

From a clone of this repo:

cd tejasetup
npm install
npx tejasetup

Screenshots

Blueprint & recommended setup

After you pick a project type, mode, and features, the CLI shows a Recommended Setup summary — stack, data tier hints, and the feature set so you can accept suggestions or continue with your own choices.

Structure & planned files

Before generation, review the folder tree and planned root files (for example package.json, .env, README.md) so you know exactly what will be created.

File preview (diff-style)

See a preview of generated files (here: Vite client entry, package.json, styles) similar to a patch view, then confirm when you are ready to write to disk.

Usage

After npm install tejasetup, prefix commands with npx (or use ./node_modules/.bin/…):

npx tejasetup                    # interactive create (default)
npx tejasetup init
npx --package=tejasetup tejas init

npx tejasetup add auth
npx tejasetup add database
npx tejasetup add logging

npx tejasetup doctor

tejas and tejasetup are the same CLI. Use -C <path> with add or doctor to point at a project directory.

Publishing to npm

Maintainers: see PUBLISHING.md for login, version bumps, npm publish, and install-command reference.

Generated output

• Stacks: React (Vite) client, Node (Express) API, Node CLI layout, and shared/ — depending on what you pick.
• Features: The CLI records choices in .tejasetup/manifest.json. Auth / database / logging add starter server and client files, not production auth.

Security

Replace demo values before production:

• JWT_SECRET and any secrets in .env
• Auth routes are demos (e.g. JWT sign without real user storage unless you wire a database)

tejas add and your stack

add applies the same dependency and stack rules as init (non-interactively): for example, enabling auth can auto-enable database where the rules require it; options that need Express are dropped if your manifest has no API server. If a feature cannot apply to your stack, the command warns you and does not change the manifest.

Project types vs templates

Many project types (Electron, React Native, extension, etc.) mainly adjust folder placeholders. The richest templates today are web, API, full-stack, CLI, and library-style layouts.

License

MIT — see LICENSE.

Repository

https://github.com/tejgokani/tejasetup — update package.json repository / bugs / homepage if you fork.