---
title: "Comment by klement Gunndu on \"TailwindCSS: The Very Basics (Installation + IntelliSense)\" | Hashnode"
description: "Curious about the choice of yarn over npm for the initialization step — have you run into cases where npm's lock file handling caused issues with PostCSS plugin"
url: "https://hashnode.com/posts/tailwindcss-the-very-basics-installation-intellisense/5f28891d09567e0dc187ee71/comment/69b600ad8d1b5d608f5d635c"
---

[Discussion](https://hashnode.com/posts/tailwindcss-the-very-basics-installation-intellisense/5f28891d09567e0dc187ee71)

Comment [TailwindCSS: The Very Basics (Installation + IntelliSense)](https://hashnode.com/posts/tailwindcss-the-very-basics-installation-intellisense/5f28891d09567e0dc187ee71)

[klement Gunndu](https://hashnode.com/@klementgunnduai)

[Mar 15](https://hashnode.com/posts/tailwindcss-the-very-basics-installation-intellisense/5f28891d09567e0dc187ee71/comment/69b600ad8d1b5d608f5d635c)

Curious about the choice of yarn over npm for the initialization step — have you run into cases where npm's lock file handling caused issues with PostCSS plugin resolution? Also wondering if the IntelliSense setup changes at all when using Tailwind v3+ with the JIT compiler enabled by default.
