[WeChat Export] Styles lost when pasting to WeChat public account - Tailwind CDN not inlined

[jackzhao9981-jpg]

Description
When using "Copy to WeChat (公众号)" feature, styles are completely lost after pasting to WeChat public account editor (mp.weixin.qq.com).

Steps to reproduce
Open html-anything at http://localhost:3000/
Select a template (e.g., deck-magazine-web or any template)
Enter some content
Click "Export" → "WeChat (公众号)"
See "已复制公众号格式" confirmation
Paste into WeChat public account article editor
All styles are lost - no background colors, no fonts, no layouts
Expected behavior
The copied HTML should retain all styles after pasting to WeChat, as the project description claims: "juice inlines CSS + data-tool markers → paste into editor, styles survive end to end."

Actual behavior
All styles are lost. The WeChat editor only shows plain text with basic formatting.

Root cause analysis
The HTML file generated includes:

<script src="https://cdn.tailwindcss.com"></script>

WeChat's editor:

Blocks/removes <script> tags (including Tailwind CDN)
Does not recognize Tailwind class names (e.g., bg-paper, text-ink)
Removes external resources (fonts, etc.)
The juice library only inlines CSS from <style> tags, but cannot process Tailwind CSS loaded via CDN because:

Tailwind classes are not in the HTML <style> tag
Tailwind is loaded dynamically via external script
juice cannot inline CDN-based CSS
Environment
Browser: Chrome (Mac)
WeChat Editor: mp.weixin.qq.com (web version)
html-anything version: latest
Possible solutions
Local Tailwind installation: Install Tailwind as a build step instead of using CDN
Full CSS inlining: Pre-process HTML to inline all Tailwind classes at build time
WeChat-specific template: Provide templates that don't rely on Tailwind for WeChat export
Documentation: Clarify that WeChat export has limitations with Tailwind-based templates

[lefarcen]

This is open for community help.

If you'd like to work on it, comment /claim below. The first /claim after the latest release gets it. Any comment, linked PR, or progress note keeps the claim active.

[lefarcen]

Hi @jackzhao9981-jpg — thanks for the very clear repro and for tracing it down to the Tailwind CDN path.

I checked the export path and your diagnosis matches the current implementation: generated documents are instructed to load Tailwind from https://cdn.tailwindcss.com, while src/lib/export/wechat.ts only collects existing <style> contents and passes that CSS into juice. That means Tailwind utility classes like bg-* / text-* never become inline styles before the HTML reaches the WeChat editor, where scripts and external resources are stripped.

I’ve marked this as a bug and help wanted. A proper fix should likely happen in the WeChat export path — either inline computed styles from the rendered preview iframe, or produce a local CSS bundle that juice can inline before copying. Documentation can be updated too, but the product promise here is that WeChat paste should preserve styling, so treating this as a real export bug makes sense.

Appreciate the detailed report — it gives whoever picks this up a strong starting point. ❤️

[lefarcen]

Hi @jackzhao9981-jpg — quick update: PR #94 is now open for the WeChat Tailwind-CDN style-loss path you reported.

That PR takes the computed-style route we discussed: it reads the live preview iframe DOM, inlines a focused set of visual styles, and keeps layout-heavy properties out so pasted content can reflow in WeChat's article column. We'll keep this issue open until the PR lands and the fix can be verified.