Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

expose as postcss plugin #5

Open
danielroe opened this issue Oct 1, 2022 · 1 comment
Open

expose as postcss plugin #5

danielroe opened this issue Oct 1, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@danielroe
Copy link
Member

For platforms supporting postcss, it would be reasonable to benefit from postcss parsing rather than the current regexp based solution (which could remain fallback)

@danielroe danielroe added the enhancement New feature or request label Oct 1, 2022
@lihbr
Copy link
Member

lihbr commented Oct 30, 2022

Just referencing some related usage.

I tried using fontaine within a Vite + PostCSS + PostCSS Import setup. The Vite plugin is not able on its own to follow import rules for now (from my own understanding of the assets being transformed directly through Vite this way, or maybe I'm doing something terribly wrong), preventing the plugin from detecting fonts as the only file detected ends up looking like the following.

@import "./abstract/fonts.css";
@import "./abstract/default.css";
@import "./abstract/typography.css";
@import "./abstract/prism.css";
@import "./abstract/theme.css";

Thanks for making fontaine 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants