npm ci vs npm install: When to Use Each

🚀 npm install vs npm ci Most developers use `npm install` daily… But in production & CI/CD, `npm ci` is the real hero ⚡ Let’s break it down 👇 --- 🔹 1. npm install 👉 What it does: * Installs dependencies from `package.json` * If `package-lock.json` exists → tries to match it * But can update versions based on rules like `^` and `~` 👉 Example: If version is `"^1.2.0"` It may install `1.3.0` instead of exact `1.2.0` ⚠️ Problem: * Different developers may get different versions * “Works on my machine” issue 😅 --- 🔹 2. npm ci 👉 What it does: * Installs EXACT versions from `package-lock.json` 🔒 * Deletes `node_modules` before install * Does NOT update anything 👉 Key Features: ✅ Faster than npm install ✅ Fully consistent installs ✅ No surprises --- 💡 When to use what? 👉 Use `npm install` * While developing * When adding new packages 👉 Use `npm ci` * In CI/CD pipelines * For production builds * When you want exact reproducibility --- 🔥 One-Line Summary: npm install → flexible but inconsistent npm ci → strict, fast & reliable #NodeJS #Angular #WebDevelopment #JavaScript #DevTips #NPM #SoftwareEngineering

Most devs know 5 git commands. Then production diverges at 3 a.m. and those 5 aren't enough. Here are 10 I actually reach for every week. 1. git reflog Your undo button. rebase, reset, force-push — reflog remembers. 2. git log --oneline --graph --all See your branch topology without opening a GUI. 3. git commit --amend --no-edit Fix the last commit. Keep the message. 4. git stash push -m "wip: auth on /users" Stash with context. Future You will thank you. 5. git blame -L 42,58 services/auth.py Blame a line range, not the whole file. 6. git rebase -i HEAD~5 Clean your PR history before review, not during it. 7. git cherry-pick <sha> Port one commit across branches. No full-branch merge. 8. git worktree add ../hotfix origin/main Two branches checked out at once. Zero context switch. 9. git bisect start HEAD v1.2 Binary-search your way to the commit that broke prod. 10. git push --force-with-lease The safe force push. Pair with --force-if-includes on git 2.30+. None of these are niche. They are the difference between a 10-minute fix and a 2-hour war room. Save this before your next git emergency. Which one saved you first — and what was the incident? One command, one sentence. #Git #SoftwareEngineering #DeveloperTips #CodingTips

You pushed clean code. The CI pipeline disagreed. Every TypeScript developer has been there. A lint error. A type mismatch. A formatting inconsistency. All things a two-second check would have caught before the commit ever happened. Instead you spend 20 minutes reverting, fixing, and pushing again. The problem is not discipline. The problem is that manual checks are not sustainable. Git has a built-in solution called hooks, scripts that run automatically before commits and pushes. But native Git hooks live in a folder that Git never tracks, which means every developer on your team has to configure them manually. The setup drifts. The protection disappears. Husky fixes this by moving your hooks into a committed folder that every developer gets automatically when they clone the project and install dependencies. One pre-commit hook runs lint and format checks with auto-fix before any code is sealed into a commit. One pre-push hook verifies types and runs the production build before anything reaches the remote. Broken code simply cannot enter the repository. You set it up once. It protects the codebase permanently. Follow me for more insights in software development. Read the full article here: https://lnkd.in/eqFJmhF8 Alain Ngongang #TypeScript #Husky #GitHooks #WebDevelopment #SoftwareDevelopment #CleanCode #DeveloperProductivity

🧠 Understanding Maven Like a Pro – The Power of pom.xml At first, multi-module projects can feel confusing… but once you understand the role of pom.xml, everything starts making sense. Think of the parent pom.xml as the brain of your entire project 🧩 🔹 It connects multiple modules into one system 🔹 It manages dependencies centrally (no repetition) 🔹 It controls the build lifecycle for all modules 🔹 It ensures consistency across the entire application 💡 Instead of managing each module separately, Maven allows you to define everything once in the parent and share it across all modules. That means: ✔ Cleaner structure ✔ Better scalability ✔ Easier maintenance ✔ Faster builds 🚀 In real-world projects (like microservices or layered architectures), this approach becomes a game changer. Once you get this concept, working with Spring Boot multi-module projects feels much more structured and powerful. #Java #Maven #SpringBoot #BackendDevelopment #CleanArchitecture #LearningJourney #SoftwareEngineering

Automation in CI can sometimes surface issues that aren't really test failures instead they're environment problems. Different OS configurations, browser/version mismatches, missing dependencies, or subtle runtime differences often lead to inconsistent results. Tests pass locally, fail in CI, or behave differently across machines, which adds noise and slows down debugging. One practical way to reduce this variability is by running tests inside a Docker container. By containerizing the setup, the execution environment becomes consistent across local and CI runs. Same OS layer, same browser versions, same dependencies every time the suite runs. Docker doesn’t solve test design issues, but it does eliminate a large class of environmental inconsistencies that often get mistaken for flaky tests. A minimal setup for a Playwright TypeScript project could look like :

There’s a pattern I keep noticing in dev teams lately. We obsess over performance, DX, and modern tooling… but when it comes to package managers, most of us still default to npm. Not because it’s the best but because it’s familiar, stable, and "just works." Meanwhile, pnpm and Bun are pushing things forward. Yet many developers: - aren’t fully clear on how pnpm’s dependency model actually works - haven’t explored how Bun replaces multiple tools at once - or simply don’t want to risk switching in production projects So npm stays the safe default. Where npm can fall short (depending on scale): - Repeated dependency duplication → higher disk usage - Slower installs in large or monorepo setups - More permissive dependency resolution (can allow hidden/implicit deps) At the same time, npm still wins on: - Zero setup (comes with Node.js) - Maximum compatibility across all packages - Stability for legacy and production systems So this isn’t really about "npm vs pnpm vs Bun" It’s about this: People focus on optimising almost every part of their stack except the defaults they got comfortable with. What’s actually stopping you from trying pnpm or Bun in your workflow? #JavaScript #NodeJS #SoftwareEngineering #WebDevelopment #npm #pnpm #Bun #DevTools

I rarely edit artifacts directly and rarely ask an LLM to fix artifacts directly. I use specs and then use Claude components (skills, rules, agents and hooks) to run those specs. If any artifacts were generated incorrectly, I have skills that fix the specs and then re-run the spec which regenerates the artifact(s). This means Claude components are continually being updated and I needed a way to re-use these components and edit them organically across all my projects. My solution: point CLAUDE_CONFIG_DIR at a git repository. Now every project runs against the same live set of skills, rules, agents, and hooks. Edits to Claude components occur in the shared git repository, even while working in another repository. Claude plugins, or similar tools, are still the right choice for distributing components to others. Wrote up the approach, the setup, and the gotchas. https://lnkd.in/gP7HZGcp

Stop wasting time waiting for 'npm install' to finish! ⏳ If you are still debating whether to switch from npm to pnpm for your real-world projects, the performance difference is more than just a minor detail—it's a productivity booster. Here is the breakdown of why pnpm is gaining massive traction: 1️⃣ Disk Space Efficiency: Unlike npm, which duplicates packages for every project, pnpm uses a content-addressable storage. This means if you have 10 projects using the same library, it’s stored only once on your disk. 2️⃣ Speed: pnpm is significantly faster. By using hard links and a clever symlink structure, it avoids the redundant copying of files, making installs lightning-fast. 3️⃣ Strictness: pnpm prevents 'phantom dependencies' by default. It doesn't flatten the `node_modules` folder, which ensures your project actually uses the packages defined in your `package.json`—leading to fewer 'it works on my machine' bugs. Verdict: - Stick with npm if you prefer the industry standard and have zero integration issues with legacy CI/CD pipelines. - Switch to pnpm if you are looking to optimize build times, save local storage, and want a more robust dependency management system. I’ve personally migrated several projects to pnpm this year and haven't looked back. What is your go-to package manager in 2026? Are you team npm, pnpm, or are you exploring Yarn/Bun? Let’s discuss in the comments! 👇 #WebDevelopment #JavaScript #NodeJS #ProgrammingTips #SoftwareEngineering #pnpm #npm #DevTooling #FullStack

𝗧𝗵𝗲 𝗖𝗹𝗮𝗎𝗱𝗲 𝗖𝗼𝗱𝗲 𝗗𝗲𝗯𝗮𝗸𝗲: 𝗚𝗨𝗜 𝗩𝗦 𝗧𝗲𝗿𝗺𝗶𝗻𝗮𝗹 I used Claude Code in the terminal for a while. It worked well with my JetBrains IDE and git branches. Then Anthropic released the GUI preview with the Opus model. I thought it would be great. But it was not. The GUI does not work in your project directory. It creates a separate git worktree. This causes issues with your IDE and git branches. You can use a workaround with VSCode, but it does not work for JetBrains users. The GUI also has issues with git worktrees. Your .env file and local config are not included. This means your app will not run. I use zsh, but the GUI only supports bash. This means my shell environment and aliases do not work. The GUI solves some problems, like session persistence and no compacting. But you can get these benefits with the terminal version and the Opus model. The terminal version gives you: - Opus-level reasoning - Your IDE working normally - Your .env and gitignored files intact - Your zsh config and PATH - Clean git workflow You can run Opus in the terminal and keep your workflow. The GUI preview is not necessary. It creates problems for developers with established workflows. The real benefits come from the Opus model, not the GUI. Source: https://lnkd.in/gMf2a9m2 Optional learning community: https://t.me/GyaanSetuAi

If you want to create a NestJS library to share between your services, you need to use peer dependencies. In short, you’re declaring that your module depends on specific packages that must be installed in the host project. pnpm add --save-peer @nestjs/{core,common} This command adds those packages as peer dependencies. Unlike npm, pnpm will also add them as dev dependencies. Note: The brace expansion syntax ({core,common}) only works on Unix-like systems. #node #pnpm #npm