A CLI tool for scaffolding a full-stack web application with your choice of frontend and backend technologies. The generated projects use npm ci and pinned Python dependencies to ensure fully deterministic and reproducible installations.
Before running the CLI or the scaffolded applications, ensure you have the following installed on your system:
To generate a new full-stack application, simply run:
npx @adriankulik/create-fullstack-app@latest
(If you are developing locally, run npm install in the root directory and execute node cli/index.js).
You will be prompted to choose a project name, your preferred frontend, and backend framework.
zone.js, testing is unified under Playwright and framework-native test runners).start.sh, test.sh, and lint.sh available out of the box to manage both frontend and backend seamlessly..github/workflows/cli-e2e.yml that tests both ends. Tip: To enforce this, enable branch protection in your GitHub repository settings and require the "test" status check to pass..vscode/extensions.json recommending the necessary linters and formatters, and an AGENTS.md file providing behavioral guidelines for AI agents. It is AI development friendly, including an extensive set of agent skills in .agents/skills.senior-frontend, senior-qa, senior-fullstack, accessibility-general
The generated application will look like this:
my-app/
├── .github/
├── .vscode/
├── backend/
│ ├── main.py
│ ├── test_main.py
│ └── requirements.txt
├── frontend/
│ ├── app/ (or src/)
│ └── package.json
├── start.sh
├── test.sh
└── lint.sh
_Note: Depending on your environment, you may need to ensure the generated shell scripts are executable by running chmod +x *.sh inside your new project directory.\
You can automatically test all frontend and backend permutations locally via Playwright integration tests using the provided script in the root directory.
Ensure you make the script executable first:
chmod +x run_e2e.sh
Then run it:
./run_e2e.sh
Note for Windows Users: The run_e2e.sh script utilizes Unix commands (like lsof and kill -9) for process teardown. You must run this script inside a WSL (Windows Subsystem for Linux) or Git Bash terminal.
Future plans for this CLI include:
This project redistributes boilerplate code and configuration files generated by the official CLIs and templates of the integrated frameworks. I'm grateful to the maintainers of these projects: