Troubleshooting

Confirm Node.js and your package manager are available. Reinstall the CLI, or use it on demand:

node --version
npm install -g forjex
forjex --version

# Run without a global installation
npx forjex --help

Your installed CLI predates starter generation. Inspect forjex --help and update after the starter release is published. Reinstalling an older published release will not add the feature.

If you are working from the Forjex source repository, build and run that local CLI:

npm run build:cli
node dist/index.js create my-app --template nextjs

Choose a different project name, or enter that folder and use the existing-project path. Forjex refuses to overwrite an existing directory, even when it is empty.

The starter files remain in the generated folder. Check your connection, Node version, and package registry access, then retry:

cd my-app
npm install
npm run dev

For Python, activate the virtual environment and install requirements. For Go and Rust, confirm the language toolchain is on your PATH.

Run the same build command locally and fix the reported errors. The CLI stops before pushing when its build check fails.

npm run build

After fixing the issue, rerun forjex forge and choose your existing project and repository. Inspect GitHub if an earlier attempt already created the repository.

• Login expired: run forjex login again and complete authorization within three minutes.
• Repository denied: verify the selected identity and its write access.
• Existing remote is empty: create an initial commit before using the browser connection flow.
• Deployment failed: inspect Vercel logs, runtime versions, build settings, and environment variables.
• Project missing from Dashboard: inspect the sync result and confirm the same account is signed in.