By the time you reach here, you must have already seen a bunch of articles explaining how to get started with two popular frameworks in the current era, Create React App (CRA) and TailwindCSS. But you may not be satisfied with their approach as it is just too much of a configuration.
The lack of visibility from the CRA team about integrating TailwindCSS, adds further confusion. I personally prefer TailwindCSS in almost all projects. It is great, smart, intuitive, and performance-friendly when used with its purge option.
Luckily, there is the official documentation on TailwindCSS that explains its integration with…
If your answer is “Yes”, then this article is for you.
Yes! you hear it right. A magical rule that scans your code against a list of browsers and probably saves a future “Hotfix”.
This rule leverages the popular MDN library for checking the JS function against a list of supported browsers.
Update: Thank you very much for your overwhelming response on original article. I’ve received a lot of request on social platforms for updating the article to support Angular 10+. So here you go… this article is an edited version of setting up Angular 6–8 universal setup on serverless framework.
With over 20+ locale-specific domains sharing the same features, it is mandatory for me to set up a scalable architecture that supports faster build time, quick deployments, ability to have a different theme and easy switching of features. This article shares my thoughts and solution to the common problems that you may face while developing multi-site architecture.
Let’s talk about the problem statement:
Since we’ve multiple sites sharing the same features, creating 20+ applications in angular.json will result in 20+ builds every time you add / update features in project. Thus, reducing the overall deployment time.
Associate Director at Cactus Communications, India. I help building highly scalable architecture for Authors and help them to publish their papers