No, there is not any need to create this file. It is optional but tailwindcss-config.js is necessary in future if you want to extend default tailwind configuration, you can do this inside this file.
Thanks for reading.
You don't seem to get my point. I meant the "tailwind.config.js" in "npx tailwindcss init tailwind.config.js -p", i feel its redundant because "npx tailwindcss init -p" gives the same result which is creating a "tailwind.config.js" file and "postcss.config.js" file
Overall it's a nice article.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
you can just do "npx tailwindcss init -p" or is there any actual need of the "tailwind.config.js" in the command?
No, there is not any need to create this file. It is optional but tailwindcss-config.js is necessary in future if you want to extend default tailwind configuration, you can do this inside this file.
Thanks for reading.
You don't seem to get my point. I meant the "tailwind.config.js" in "npx tailwindcss init tailwind.config.js -p", i feel its redundant because "npx tailwindcss init -p" gives the same result which is creating a "tailwind.config.js" file and "postcss.config.js" file
Overall it's a nice article.