Skip to content

Document known HMR issue with CSS Modules - #25002

Closed
ricsam wants to merge 1 commit into
oven-sh:mainfrom
ricsam:patch-2
Closed

ricsam wants to merge 1 commit into
oven-sh:mainfrom
ricsam:patch-2

Conversation

@ricsam

@ricsam ricsam commented Nov 23, 2025 •

Copy link
Copy Markdown

What does this PR do?

Added a warning about known issues with HMR and CSS Modules in the docs.

How did you verify your code works?

Previewed the documentation updates

Added a warning about known issues with HMR and CSS Modules.
@coderabbitai

coderabbitai Bot commented Nov 23, 2025 •

Copy link
Copy Markdown
Contributor

Walkthrough

Added warning documentation about a known HMR bug for CSS Modules to the CSS bundler documentation. The warnings were inserted in two locations within the CSS Modules sections, clarifying that the issue occurs only during development with HMR enabled.

Changes

Cohort / File(s) Change Summary
Documentation updates
docs/bundler/css.mdx
Added warning blocks detailing a known HMR bug for CSS Modules (issue #18258) in two locations within the CSS Modules documentation, specifying that the issue occurs only in development with HMR enabled

Pre-merge checks

✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: adding documentation about a known HMR issue with CSS Modules, which matches the file changes in docs/bundler/css.mdx.
Description check ✅ Passed The pull request description follows the required template with both sections completed appropriately.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@robobun

robobun commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

A fix for the underlying bug is in review in #42058. Once it merges, import styles from "./x.module.css" works under the dev server with HMR, and this note would no longer be needed.

@ricsam ricsam closed this Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants