@css-everything/render
Advanced tools
A ui library where you only write CSS. No HTML, no JS, no build system, only CSS (kinda).
A ui library where you only write CSS. No HTML, no JS, no build system, only CSS (kinda).
Disclaimer: Don't use this
WIP. Coming soon maybe?
You can start by adding the script tag for the renderer inside the body
<!-- index.html -->
<html lang="en">
<head>
<link href="./style.css" rel="stylesheet" />
</head>
<body>
<script async defer src="https://unpkg.com/@css-everything/render@0.0.1/dist/renderer/index.js"></script>
</body>
</html>
NOTE: The HTML needs to have a body element since that is the root of your application by default.
NOTE_v2: Styles need to be loaded before the renderer is triggered.
NOTE_v2_final: You can load more cssx by using the load-cssx() function
/* style.css */
:root {
/* creates 2 elements main and button */
--cssx-children: main#main-el button#my-button;
}
#main-el {
--text: "<stuff>";
}
#main-el::after {
content: var(--text);
}
#my-button {
--cssx-text: "Click me";
/* On click, waits for 1 second and then updates the --text property #main-el */
--cssx-on-click: update(main-el, --text, "Loading...") delay(1s)
update(main-el, --text, "Hello world!");
}
"Wow. You couldn't come up with a more boring example if you tried."
Alright. You don't have to be mean about it.
Why not?
What?
Why don't you ask that to this example?
It starts by reading the --cssx-children property on the body. Which is then parsed and evaluated and the necassary child nodes are created.
For each element that is managed by cssx (i.e. not created via js or html or --cssx-disgustingly-set-innerhtml or js-eval), we then look for event handler properties present on the node. These properties are parsed and evaluated when the relevant event is triggered.
No. The browser does most of it. Only the fancy --cssx-* properties use a custom parser.
FAQs
#### Add script tag to the renderer to your html ```html <script async defer src="https://unpkg.com/@css-everything/render/dist/renderer/index.js"></script> ```
The npm package @css-everything/render receives a total of 0 weekly downloads. As such, @css-everything/render popularity was classified as not popular.
We found that @css-everything/render demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.