storybookjs/storybook

[Bug]: No TailwindCSS classes reload after Angular component save. Need to refresh the whole page to get styles. Hot-reload issue?

Open

#26,122 opened on Feb 20, 2024

View on GitHub
 (2 comments) (1 reaction) (0 assignees)TypeScript (10,058 forks)batch import
angularbughelp wantedsev:S3tailwind

Repository metrics

Stars
 (89,909 stars)
PR merge metrics
 (Avg merge 7d 22h) (184 merged PRs in 30d)

Description

Describe the bug

What is wrong

  1. After installation of Angular 17 (newest) + Tailwind (newest) + Storybook (newest) there is a hot reloading issue, in which Storybook refreshes on angular component save but doesn't deliver newest CSS styles. Classes gets applied, but classes definition is not carried into them. To get the proper styling you have to manually refresh the window, then they are present. I suspect hot-reload occurs before new CSS are compiled by Tailwind and ready to use, or hot reload doesn't force new files fetching.

Project installed according to: https://tailwindcss.com/docs/guides/angular https://storybook.js.org/recipes/tailwindcss

To Reproduce

Install newest angular and follow: https://tailwindcss.com/docs/guides/angular https://storybook.js.org/recipes/tailwindcss

System

No response

Additional context

No response

Contributor guide

Research direction
Investigate the hot module replacement (HMR) pipeline for Angular components in Storybook. Ensure TailwindCSS compilation is triggered before the component update. Check if the issue is related to the order of CSS file injection during hot reload.
Tech stack
typescriptangulartailwindcssstorybook
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
AngularTailwindCSSStorybook
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50