@inglorious/web 4.0.8 → 4.0.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -5
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -32,8 +32,8 @@ Unlike modern frameworks that invent their own languages or rely on signals, pro
|
|
|
32
32
|
- **Zero Component State**
|
|
33
33
|
All state lives in the store — never inside components.
|
|
34
34
|
|
|
35
|
-
- **No Signals, No Subscriptions, No Memory Leaks**
|
|
36
|
-
Because every render is triggered by the store, and lit-html handles the rest.
|
|
35
|
+
- **No Signals, No Subscriptions, No Framework-Level Memory Leaks**
|
|
36
|
+
Because every render is triggered by the store, and lit-html handles the rest — no subscription cleanup needed.
|
|
37
37
|
|
|
38
38
|
- **No compilation required**
|
|
39
39
|
Apps can run directly in the browser — no build/compile step is strictly necessary (though you may use bundlers or Vite for convenience in larger projects).
|
|
@@ -60,6 +60,8 @@ Use the scaffolder to create a starter app tailored to your workflow.
|
|
|
60
60
|
|
|
61
61
|
### ✨ **Inglorious Web re-renders the whole template tree on each state change.**
|
|
62
62
|
|
|
63
|
+
**Important:** The DOM itself is not re-created. Only the template function reruns, and lit-html's efficient diffing updates just the changed DOM nodes.
|
|
64
|
+
|
|
63
65
|
Thanks to lit-html's optimized diffing, this is fast, predictable, and surprisingly efficient.
|
|
64
66
|
|
|
65
67
|
This means:
|
|
@@ -93,7 +95,7 @@ This framework is ideal for both small apps and large business UIs.
|
|
|
93
95
|
|
|
94
96
|
## When NOT to Use Inglorious Web
|
|
95
97
|
|
|
96
|
-
- You
|
|
98
|
+
- You're frequently mutating thousands of items without virtualization (though our `list` component handles this elegantly)
|
|
97
99
|
- You're building a library that needs to be framework-agnostic
|
|
98
100
|
- Your team is already deeply invested in React/Vue/Angular
|
|
99
101
|
|
|
@@ -141,7 +143,21 @@ This makes it especially suitable for:
|
|
|
141
143
|
|
|
142
144
|
## Comparison with Other Frameworks
|
|
143
145
|
|
|
144
|
-
|
|
146
|
+
### TL;DR Quick Comparison
|
|
147
|
+
|
|
148
|
+
| Framework | Reactivity | Compiler | Component State | Bundle Size | Learning Curve |
|
|
149
|
+
| -------------- | -------------- | -------- | --------------- | ----------- | -------------- |
|
|
150
|
+
| Inglorious Web | Event-based | None | No (store only) | Tiny | Very Low |
|
|
151
|
+
| React | VDOM diffing | None | Yes | Large | Medium/High |
|
|
152
|
+
| Vue | Proxy-based | Optional | Yes | Medium | Medium |
|
|
153
|
+
| Svelte | Compiler magic | Required | Yes | Small | Medium |
|
|
154
|
+
| SolidJS | Fine signals | None | No (runs once) | Tiny | Medium/High |
|
|
155
|
+
| Qwik | Resumable | Required | Yes | Small | Very High |
|
|
156
|
+
|
|
157
|
+
<details>
|
|
158
|
+
<summary><strong>Click to expand detailed framework comparisons</strong></summary>
|
|
159
|
+
|
|
160
|
+
Here's how @inglorious/web compares to the major players in detail:
|
|
145
161
|
|
|
146
162
|
---
|
|
147
163
|
|
|
@@ -220,6 +236,8 @@ Inglorious Web is minimal, predictable, and tiny.
|
|
|
220
236
|
|
|
221
237
|
Inglorious Web is closer philosophically to **HTMX** and **vanilla JS**, but with a declarative rendering model and entity-based state.
|
|
222
238
|
|
|
239
|
+
</details>
|
|
240
|
+
|
|
223
241
|
---
|
|
224
242
|
|
|
225
243
|
## Why Choose Inglorious Web
|
|
@@ -231,7 +249,7 @@ Inglorious Web is closer philosophically to **HTMX** and **vanilla JS**, but wit
|
|
|
231
249
|
- One render path, no hidden rules
|
|
232
250
|
- No reactivity graphs
|
|
233
251
|
- No per-component subscriptions
|
|
234
|
-
- No memory leaks
|
|
252
|
+
- No framework-level memory leaks
|
|
235
253
|
- No build step required (apps can run in the browser)
|
|
236
254
|
- Works perfectly in hybrid UI/game engine contexts
|
|
237
255
|
- Uses native ES modules and standards
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@inglorious/web",
|
|
3
|
-
"version": "4.0.
|
|
3
|
+
"version": "4.0.9",
|
|
4
4
|
"description": "A new web framework that leverages the power of the Inglorious Store combined with the performance and simplicity of lit-html.",
|
|
5
5
|
"author": "IceOnFire <antony.mistretta@gmail.com> (https://ingloriouscoderz.it)",
|
|
6
6
|
"license": "MIT",
|
|
@@ -68,8 +68,8 @@
|
|
|
68
68
|
"dependencies": {
|
|
69
69
|
"@lit-labs/ssr-client": "^1.1.8",
|
|
70
70
|
"lit-html": "^3.3.1",
|
|
71
|
-
"@inglorious/
|
|
72
|
-
"@inglorious/
|
|
71
|
+
"@inglorious/utils": "3.7.2",
|
|
72
|
+
"@inglorious/store": "9.0.1"
|
|
73
73
|
},
|
|
74
74
|
"devDependencies": {
|
|
75
75
|
"prettier": "^3.6.2",
|