Yesterday we learned how to set up our first Angular project. Today we will be adding Tailwind CSS so we can easily use its simplicity in styling components.
Note: when setting up your project, make sure you select
SCSS.
Tailwind is a CSS framework, much like bootstrap, but it doesn't include any card or navbar components.
We can call it a utility framework. It makes use of utility classes like: shadow-lg, rounded, w-full, etc.
At the time of writing, I'm using Angular 10 and Tailwind 1.8
Adding Tailwind CSS to our app
Ok, so we set up our basic Angular application, now let's add the Tailwind package.
Open your terminal and run the following command to install Tailwind
npm install tailwindcss -D
Then we need the ngx-build-plus package.
npm install ngx-build-plus
We also need various postcss packages and a custom web pack builder.
npm install postcss-scss postcss-import postcss-loader -D
That's all the installs. We now need a webpack.config.js file in the root of our project.
This file will have the following content.
module.exports = {
module: {
rules: [
{
test: /\.scss$/,
loader: 'postcss-loader',
options: {
postcssOptions: {
ident: 'postcss',
syntax: 'postcss-scss',
plugins: [
require('postcss-import'),
require('tailwindcss'),
require('autoprefixer'),
],
},
},
},
],
},
};
I won't go in to much detail, but we are creating webpack rules so that we can run SCSS in our application. And register tailwind as a plugin.
Next up, we need to change our angular.json file to tell it we created this custom webpack file.
Open your editor and make the following changes.
- build/builder:
ngx-build-plus:browser - ✚ add line:
"options": {
"extraWebpackConfig": "webpack.config.js",
}
- serve/builder:
ngx-build-plus:dev-server - ✚ add line:
"options": {
"extraWebpackConfig": "webpack.config.js",
},
Adding the Tailwind styles
Now it's time to add the Tailwind css to our application.
Open the styles.scss file, you can find it in the src folder.
Add the following lines.
@import 'tailwindcss/base';
@import 'tailwindcss/components';
@import 'tailwindcss/utilities';
This tells our application to import all the Tailwind default CSS styles.
Now we need to init our Tailwind by running the following code in our terminal.
npx tailwind init
This will create a tailwind.config.js file for us.
Using Tailwind in our Angular application
We can now go ahead and try out our new Tailwind CSS.
Let's open up our welcome.component.html file and make the following changes.
<div class="fixed z-10 inset-0 overflow-y-auto">
<div class="flex items-end justify-center min-h-screen pt-4 px-4 pb-20 text-center sm:block sm:p-0">
<div class="fixed inset-0 transition-opacity">
<div class="absolute inset-0 bg-gray-500 opacity-75"></div>
</div>
<span class="hidden sm:inline-block sm:align-middle sm:h-screen"></span>​
<div class="inline-block align-bottom bg-white rounded-lg text-left overflow-hidden shadow-xl transform transition-all sm:my-8 sm:align-middle sm:max-w-lg sm:w-full" role="dialog" aria-modal="true" aria-labelledby="modal-headline">
<div class="bg-white px-4 pt-5 pb-4 sm:p-6 sm:pb-4">
<div class="sm:flex sm:items-start">
<div class="mx-auto flex-shrink-0 flex items-center justify-center h-12 w-12 rounded-full bg-red-100 sm:mx-0 sm:h-10 sm:w-10">
<!-- Heroicon name: exclamation -->
<svg class="h-6 w-6 text-red-600" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor">
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 9v2m0 4h.01m-6.938 4h13.856c1.54 0 2.502-1.667 1.732-3L13.732 4c-.77-1.333-2.694-1.333-3.464 0L3.34 16c-.77 1.333.192 3 1.732 3z" />
</svg>
</div>
<div class="mt-3 text-center sm:mt-0 sm:ml-4 sm:text-left">
<h3 class="text-lg leading-6 font-medium text-gray-900" id="modal-headline">
Deactivate account
</h3>
<div class="mt-2">
<p class="text-sm leading-5 text-gray-500">
Are you sure you want to deactivate your account? All of your data will be permanently removed. This action cannot be undone.
</p>
</div>
</div>
</div>
</div>
<div class="bg-gray-50 px-4 py-3 sm:px-6 sm:flex sm:flex-row-reverse">
<span class="flex w-full rounded-md shadow-sm sm:ml-3 sm:w-auto">
<button type="button" class="inline-flex justify-center w-full rounded-md border border-transparent px-4 py-2 bg-red-600 text-base leading-6 font-medium text-white shadow-sm hover:bg-red-500 focus:outline-none focus:border-red-700 focus:shadow-outline-red transition ease-in-out duration-150 sm:text-sm sm:leading-5">
Deactivate
</button>
</span>
<span class="mt-3 flex w-full rounded-md shadow-sm sm:mt-0 sm:w-auto">
<button type="button" class="inline-flex justify-center w-full rounded-md border border-gray-300 px-4 py-2 bg-white text-base leading-6 font-medium text-gray-700 shadow-sm hover:text-gray-500 focus:outline-none focus:border-blue-300 focus:shadow-outline-blue transition ease-in-out duration-150 sm:text-sm sm:leading-5">
Cancel
</button>
</span>
</div>
</div>
</div>
</div>
Note: You can find more examples on the Tailwind component page.
Now, if we run ng serve, we should see the following result.
You can also find this project on GitHub.
Thank you for reading, and let's connect!
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter
Top comments (10)
For someone who doesnot want to write css, tailwind css be a good thing. But for large scale projects this can be a disaster to manage.
I started using this for a project of mine but discarded it halfway as the utility based classes were becoming unmanageable.
Currently trying to implement in a large-scale project and we are really trying to wrap our head around management.
And being uniform
Not the easiest thing to do believe me. One class of multiple components VS lots of classes for each component, on top of that you have to manage mobile reponsiveness as well. I would suggest using bootstrap instead if you are not opting for custom CSS, makes CSS management a whole lot easier.
Hmm let's see we have one guy who is fully into tailwind already so hoping he can steer us into the right direction.
Not an angular person but using Tailwind for quite some time now.
On the tailwind website the common information is that you shall use components as a single source of truth, meaning it doesn't matter if you need 20 utility classes. Your 1 component can be easily managed and changed.
If you want to create a button, you'd create a button component that holds all the styling.
This can be read in way better words than I can explain here. I personally completely avoid
@apply. I'd rather create a component.For global uniformity you can change a lot in the tailwind-config. So if you always want your baseline
shadowto be a specific value, go ahead and change it to that. All of your devs can then just useshadowand be happy with the results. This process can be applied to anything within Tailwind.Since Tailwind is the way it is, it may require some configuration on your end if your team is getting big and you start to notice some inconsistencies.
What really helps is to structure the order in which you use your css classes.
For example, instead of saying:
you could group the relevant info together
This is obviously optional. It personally helps me to find classes faster because they always have their place.
Also, on the more practical side:
If you're using VsCode, this is an absolute life-saver
Ohh nice! yes, recently added this plugin as well!
To do the order of the classes
Nice to see a Tailwind installation guide for Angular 😃
I wrote one for Vue 😊
Does the default PurgeCSS config of Tailwind work without changes for Angular projects?
It is supposed to yes, haven't come to that part yet.
Will likely test that out soon.
So, what are your impressions about Tailwind? 👀
I've heard a lot of great things about it from devs 🤩
So far it's been super useful, but really wrapping my head around some things still:
The main classes make dev super quick though, currently just using some extra styling for the stuff I'm missing.