Git Basics and Live Environments for Web Development

Just built a Git Activity Dashboard CLI using Node.js! It runs inside any git repository and provides a terminal summary that includes: - Current branch and file status - Recent commits — detailing who did what and when - Top contributors displayed with a visual bar chart - Files changed in the last commit, including lines added and removed The interesting part is that it utilizes the Node.js child_process module. Instead of relying on any git library, it spawns git status, git log, and git diff as separate child processes to collect their output, just like your terminal does. All four commands run in parallel using Promise.all, ensuring the dashboard loads instantly. There are zero heavy dependencies—just Node.js and chalk. GitHub: https://lnkd.in/gSD2hTG8 #nodejs #javascript #buildinpublic #opensource

Just shipped an update to aicommit. What’s new: - Works with both Codex and Claude Code - Smarter provider selection with explicit --provider codex|claude - Better end-user docs The goal is simple: make AI-assisted commit messages easier to use in real developer workflows, without locking anyone into a single coding CLI. Install: npm install --global @ahalberkamp/aicommit Usage: aicommit aicommit --provider codex aicommit --provider claude Repo: https://lnkd.in/dbmj2wnY #opensource #javascript #nodejs #cli #git #developertools #ai #codex #claudecode #productivity

I got tired of Claude forgetting everything between sessions. So I built an orchestration layer that fixes the operational gaps Claude Code doesn't cover: → One git repo syncs instructions across every machine → Context loads per project... Next.js gets Next.js rules, not PHP ones → Secrets never touch agent context, process-scoped, vanish on exit → A bash worker pulls backlog tasks, runs in Docker, commits, and repeats, unattended One bootstrap script. Idempotent. Cross-platform. ctrlshft.dev

🚀 One push to main. Six Laravel starter kits rebuilt and deployed automatically. Zero manual steps. I contributed to a private automation repo built by Pushpak Chhajed that generates 6 production-ready Laravel starter kits. It includes Vue, React, and Livewire, each with and without auth, and publishes them to separate GitHub repos every night at 2 AM ⏰ 🔥 What’s included out of the box: - PHPStan for static analysis - Rector + Pint for auto-formatting ✨ - Pest with strict type coverage 🧪 - Pre-generated IDE helper files - composer test runs everything in one command ⚡ ⚙️ The whole pipeline is powered by a single bash script. GitHub Actions runs a matrix job to build all 6 in parallel 🧵 jq patches composer.json directly, so there are no stale stub files ❌📦 🧠 Wrote a detailed breakdown of how it works: https://lnkd.in/gg8Z7KwN

⚡ 𝗻𝗽𝗺 𝗶𝗻𝘀𝘁𝗮𝗹𝗹 𝘃𝘀 𝗻𝗽𝗺 𝗰𝗶 — Quick Dev Tip Most developers use these daily, but using the right one actually matters 👇 🔧 𝗻𝗽𝗺 𝗶𝗻𝘀𝘁𝗮𝗹𝗹   • Best for development   • Installs from package.json   • Can update dependencies  ⚡ 𝗻𝗽𝗺 𝗰𝗶   • Best for CI/CD & production   • Installs exact versions from package-lock.json   • Fast, clean & consistent every time  💡 𝗦𝗶𝗺𝗽𝗹𝗲 𝗿𝘂𝗹𝗲: 👉 Local work → npm install   👉 Builds & deployments → npm ci  Avoid “works on my machine” issues by choosing the right command 🚀 #nodejs #javascript #npm #webdev #devtips

Do you want to keep your commit history and merge two repos into one (say frontend and backend) or split one repo in two (say service-a and service-b)? May I introduce you to the `git subtree pull` and `git subtree split` commands? First you have to add the repo you want to migrate from/to as another remote. Then you can continuously: git subtree pull \ --prefix new-repo-folder \ other-remote-name \ branch-you-want-to-pull And done. Your other repo is now included in the folder new-repo-folder. Including commit history. Including all commits after the initial pull. git subtree split is the inverse command where you take something in a folder and move it to another remote. That one I haven’t used though, but it’s useful to know nonetheless. I’ll post a real tutorial once I have time, but this is too useful to know :)

Every time I joined a new git repo I'd run: ``` git log --oneline git shortlog -sn git diff --stat ``` ...and mentally piece the context together. So I built a CLI tool to do it in one command with beautiful interface in the command line: ``` npx gitbrew ``` You get an instant terminal dashboard — contributor stats, commit activity sparkline, hotspot files, and current working tree changes. All rendered with Ink (React for CLIs). Stack: TypeScript, Ink, simple-git, Commander. Supports time windows (--since 7d or -s 7d), author filter (--author <name> or -a <name>), and JSON output for piping. Try it in any git repo: ``` npx gitbrew ``` or install globally and run it simply: ``` npm install -g gitbrew gitbrew ``` npm: https://lnkd.in/gSiSiWMq GitHub: https://lnkd.in/gRvRkGqS #opensource #nodejs #typescript #cli #javascript

💀 “It works on my machine” — until npm says NO. Today I went down a rabbit hole trying to understand a simple question: 👉 Why does npm sometimes REFUSE to install packages? No syntax error. No wrong code. Still… everything breaks. Here’s what I learned 👇 There’s a hidden rule in Node.js projects called peerDependencies. Think of it like this: 🧩 Some packages don’t bring their own dependencies They EXPECT you to already have the correct version installed And if you don’t? 💥 npm throws ERESOLVE 💥 Installation fails 💥 Your patience disappears Real example: ts-jest wanted 👉 @types/jest v27 Project had 👉 @types/jest v24 Result? ❌ Conflict 💡 The lesson: ✔ Not all dependencies are independent ✔ Version mismatch = silent chaos ✔ npm is strict for a reason (it’s saving you from future bugs) The fix was simple. The understanding was not. 🚀 That’s the real growth in development: Not fixing errors… But understanding why they exist If you've ever deleted node_modules and prayed… #NodeJS #npm #WebDevelopment #Debugging #SoftwareEngineering #FullStackDeveloper

⚡Zod v4 — The TypeScript Validation Library Just Got a Complete Overhaul 🚀 The most popular TypeScript validation library just shipped a major rewrite — and it’s a game‑changer. Zod v4 is 3× faster, smaller, and introduces a Valibot‑style pipe API that makes complex validations feel effortless. 💡 Highlights: ⚙️ 3× faster parsing and leaner bundle size 🌐 New z.string().url() and z.email() primitives 🔗 Functional pipe API for cleaner composition 🧩 z.toJSONSchema() for OpenAPI and Swagger integration 🧠 Improved TypeScript inference and runtime performance 🧑💻 Whether you’re building APIs, forms, or full‑stack apps, Zod v4 makes validation smarter, faster, and more expressive. 👉 Dive into the full deep‑dive guide with benchmarks, migration tips, and real‑world examples: “Zod v4: The TypeScript Validation Library Just Got a Complete Overhaul” #Zod #TypeScript #WebDevelopment #Validation #Frontend #Backend #JavaScript #DevTools #Programming #Developers