2022-06-02
1585
#react
Lawrence Eagles
114006
Jun 2, 2022 ⋅ 5 min read

Setting up a dev environment with React, Vite, and Tailwind

Lawrence Eagles Senior full-stack developer, writer, and instructor.

Recent posts:

JavaScript Dictionary

JavaScript dictionary: How to use objects and maps for key-value pairs

Learn how to use JavaScript dictionaries with Objects and Maps. Discover key differences, performance insights, and best use cases with practical examples.

Elijah Agbonze
Feb 25, 2025 ⋅ 9 min read
A guide to the CSS grid-template-columns property

A guide to the CSS grid-template-columns property

Take a deep dive into the CSS grid template columns property, an essential part of the CSS Grid Layout specification.

Samuel Martins
Feb 25, 2025 ⋅ 15 min read
A Guide To Node.js Readable Streams

A guide to Node.js readable streams

Explore how Node.js readable streams process data in small chunks, manage data flow, handle errors, and ensure resource cleanup.

Yan Sun
Feb 25, 2025 ⋅ 7 min read
Advanced React State Management Using URL Parameters

Advanced React state management using URL parameters

Manage state in React using URL parameters for better performance, SEO, and accessibility while enabling shareable and server-rendered application states.

Rahul Chhodde
Feb 24, 2025 ⋅ 16 min read
View all posts

3 Replies to "Setting up a dev environment with React, Vite, and Tailwind"

  1. Nice article.

    Please review your tailwind.config.js file…

    You still need to add index.html into the content array.

    Vite injection point is index.html which is not inside the src folder like react did theirs..

    Great work!

  2. It seems that in this tutorial the “type” in package.json gets set to “module” which is in direct conflict with the config.js files of postcss and tailwind as they use the “require” syntax.
    When running the appications it exits with an error because of that. Only solution I found was to remove the “type” in package.json. Not sure, if this is a good solution though.

  3. Very nice article. I found it very useful and informative.
    There was an error when creating the postcss.config.js file and the error was thrown because the name should be postcss.config.cjs and not .js. I just wanted to point it out for anyone that might find it useful.

Leave a Reply