A personal TypeScript playground for experimenting with basic logic, utility functions, and language features. This repository serves as a hands-on space to build, refactor, and explore foundational programming concepts through small, self-contained tasks.
TypeBrew is a focused repository for practicing TypeScript syntax and programming patterns. Each file represents a small
task or utility function, often paired with a .txt file that explains the problem, requirements, or challenge
objective.
Whether it's string manipulation, math operations, or logic-based conditions, this project is built for iterating on ideas and improving fluency with TypeScript.
type-brew/
│
├── src/
│ ├── tasks/ # Contains individual task implementations and descriptions
│ │ ├── task-name.ts # TypeScript implementation of a specific task
│ │ ├── task-name.txt # Description or notes for the task
│ │ └── ...
│ └── playground/ # Sandbox area for testing and quick experimentation
│
├── package.json
├── tsconfig.json
├── vite.config.ts
└── README.md
Each task follows a simple format:
.tsfiles for TypeScript logic..txtfiles for task descriptions, goals, or notes.
git clone https://github.com/Friftycode/type-brew.git
cd TypeBrewNote: The project depends on several external packages including Vite, React, and TypeScript. Make sure to install dependencies before running.
npm installYou can use ts-node or compile and run using tsc.
# Option 1: Run directly with ts-node (recommended)
npx ts-node src/tasks/your-task-file.ts
# Option 2: Compile then run
tsc src/tasks/your-task-file.ts
node src/tasks/your-task-file.js- Each file in the src/tasks/ folder is a standalone TypeScript task.
- Open any .txt file to read the task description.
- Open the corresponding .ts file to view or modify the solution.
- You can experiment, refactor, or expand on the logic as needed.
This structure is ideal for:
- Practicing coding interview-style questions.
- Revising language syntax and control structures.
- Testing logic and functional programming in TypeScript.
- Task-Oriented Each challenge is scoped narrowly to isolate learning objectives.
- Text + Code Pairing
Descriptions are written in
.txtfiles to mirror real problem statements. - Iterative Practice Older tasks can be revisited and refactored. Emphasis on clarity, readability, and clean function structure.
- Formatting Consistency Code is formatted consistently for readability and maintenance.