We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If you visit a demo of any component on localhost:8080 and change that component's CSS, those changes are not reflected in the localhost:8080 demo.
They are reflected in the dev server (localhost:8000).
staging/clefairy
clefairy
npm run start
elements/rh-badge/rh-badge.css
You can follow these same steps with any component—not just badge.
The docs server should watch and compile CSS changes to components so that you can view their demos.
iOS, macOS, Linux, Windows
Chrome, Safari, Safari iOS, Microsoft Edge, Firefox
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
Looks like you're on the dev server (8000), not the docs server (8080).
This issue still exists in my testing on staging/clefairy.
Gotcha. Known issue. Huge headache. Maybe eleventy 3 will help (wishful thinking). Kicked to cubone, with apologies.
No branches or pull requests
Describe the bug
If you visit a demo of any component on localhost:8080 and change that component's CSS, those changes are not reflected in the localhost:8080 demo.
They are reflected in the dev server (localhost:8000).
Steps to reproduce
staging/clefairy
or any branch off ofclefairy
.npm run start
elements/rh-badge/rh-badge.css
.You can follow these same steps with any component—not just badge.
Expected behavior
The docs server should watch and compile CSS changes to components so that you can view their demos.
Operating System (OS)
iOS, macOS, Linux, Windows
Browser
Chrome, Safari, Safari iOS, Microsoft Edge, Firefox
The text was updated successfully, but these errors were encountered: