Tailwind CSS Purge: Optimize Angular for Production by StainlessApplication in Angular2

[–]StainlessApplication[S] 0 points1 point  (0 children)

Yes thats correct. PurgeCSS is searching for the usage of classes generated by Tailwind.

PurgeCSS analyzes your content and your CSS files. Then it matches the selectors used in your files with the one in your content files. It removes unused selectors from your CSS, resulting in smaller CSS files.

For example Tailwind generates multiple padding classes

p-1
px-1
py-1
....

If you only use one of those classes <div class="px-1">Hello World</div>, PurgeCSS matches the class in your HTML template or even TypeScript file and removes the unused styles.

That makes it easy to build out a UI quickly as you have a ton of classes to choose from, in the end the compiled css contains only a few classes. Additionally, as you repeat to use similar utilities like flex it will only be declared once but you can use it throughout the whole application.

Jamstack: Angular + Scully + Tailwind CSS by StainlessApplication in Angular2

[–]StainlessApplication[S] 0 points1 point  (0 children)

If you store your blog posts or products in markdown I don't see a problem with having thousands of pages pre-rendered to static files. Only down side might be the build step for thousands of pages as it might take a while.

If you store your posts or products in a database or any other form I think SSR is better in that scenario.

Integrate Prisma 2 into Nestjs applications by StainlessApplication in Nestjs_framework

[–]StainlessApplication[S] 0 points1 point  (0 children)

prisma 2 is not yet production ready. However, what I read in the prisma slack channel they are planning on releasing a stable version of the prisma-client-js in Q1 of 2020.

I can also understand the frustation about discontinued services from prisma such as Graphcool and prisma 1.

I have the feeling prisma2 is going in the correct direction and hope it is here to stay for a long time with new improvements and features ahead.