@inglorious/store 7.1.1 → 7.1.3

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.
Files changed (2) hide show
  1. package/README.md +8 -8
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -831,16 +831,16 @@ Now, your store is fully type-safe. The hooks provided by `@inglorious/react-sto
831
831
 
832
832
  Check out the following demos to see the Inglorious Store in action on real-case scenarios:
833
833
 
834
- - **[TodoMVC](https://github.com/IngloriousCoderz/inglorious-engine/tree/main/examples/apps/todomvc)** - An (ugly) clone of Kent Dodds' [TodoMVC](https://todomvc.com/) experiments, showing the full compatibility with react-redux and The Redux DevTools.
835
- - **[TodoMVC-CS](https://github.com/IngloriousCoderz/inglorious-engine/tree/main/examples/apps/todomvc-cs)** - A client-server version of the TodoMVC, which showcases the use of `notify` as a cleaner alternative to `dispatch` and async event handlers.
836
- - **[TodoMVC-RT](https://github.com/IngloriousCoderz/inglorious-engine/tree/main/examples/apps/todomvc-rt)** - A "multiplayer" version, in which multiple clients are able to synchronize through a real-time server.
837
- - **[TodoMVC-TS](https://github.com/IngloriousCoderz/inglorious-engine/tree/main/examples/apps/todomvc-ts)** - A typesafe version of the base TodoMVC.
834
+ **React Examples:**
838
835
 
839
- ---
836
+ - **[React TodoMVC](https://github.com/IngloriousCoderz/inglorious-forge/tree/main/examples/apps/react-todomvc)** - An (ugly) clone of Kent Dodds' [TodoMVC](https://todomvc.com/) experiments, showing the full compatibility with react-redux and The Redux DevTools.
837
+ - **[React TodoMVC-CS](https://github.com/IngloriousCoderz/inglorious-forge/tree/main/examples/apps/react-todomvc-cs)** - A client-server version of the TodoMVC, which showcases the use of `notify` as a cleaner alternative to `dispatch` and async event handlers.
838
+ - **[React TodoMVC-RT](https://github.com/IngloriousCoderz/inglorious-forge/tree/main/examples/apps/react-todomvc-rt)** - A "multiplayer" version, in which multiple clients are able to synchronize through a real-time server.
839
+ - **[React TodoMVC-TS](https://github.com/IngloriousCoderz/inglorious-forge/tree/main/examples/apps/react-todomvc-ts)** - A typesafe version of the base TodoMVC.
840
840
 
841
- ## Part of the Inglorious Engine
841
+ For more demos and examples with `@inglorious/web`, see the [`@inglorious/web` README](../web/README.md).
842
842
 
843
- This store powers the [Inglorious Engine](https://github.com/IngloriousCoderz/inglorious-engine), a functional game engine. The same patterns that power games power your web apps.
843
+ ---
844
844
 
845
845
  ## Frequently Unsolicited Complaints (FUCs)
846
846
 
@@ -866,7 +866,7 @@ It looks like it's not, and that's a feature. If you're used to classes and inst
866
866
 
867
867
  **"This is not Data-Oriented Design."**
868
868
 
869
- It's not. Please grep this README and count how many occurrences of DoD you can find. This is not [Data-Oriented Design](https://en.wikipedia.org/wiki/Data-oriented_design), which is related to low-level CPU cache optimization. It's more similar to [Data-Driven Programming](https://en.wikipedia.org/wiki/Data-driven_programming), which is related to separating data and behavior. The Inglorious Engine separates behavior in... behaviors (grouped into so-called types), while the data is stored in plain objects called entities.
869
+ It's not. Please grep this README and count how many occurrences of DoD you can find. This is not [Data-Oriented Design](https://en.wikipedia.org/wiki/Data-oriented_design), which is related to low-level CPU cache optimization. It's more similar to [Data-Driven Programming](https://en.wikipedia.org/wiki/Data-driven_programming), which is related to separating data and behavior. The Inglorious Store separates behavior in... behaviors (grouped into so-called types), while the data is stored in plain objects called entities.
870
870
 
871
871
  ---
872
872
 
package/package.json CHANGED
@@ -1,17 +1,17 @@
1
1
  {
2
2
  "name": "@inglorious/store",
3
- "version": "7.1.1",
3
+ "version": "7.1.3",
4
4
  "description": "A state manager for real-time, collaborative apps, inspired by game development patterns and compatible with Redux.",
5
5
  "author": "IceOnFire <antony.mistretta@gmail.com> (https://ingloriouscoderz.it)",
6
6
  "license": "MIT",
7
7
  "repository": {
8
8
  "type": "git",
9
- "url": "git+https://github.com/IngloriousCoderz/inglorious-engine.git",
9
+ "url": "git+https://github.com/IngloriousCoderz/inglorious-forge.git",
10
10
  "directory": "packages/store"
11
11
  },
12
12
  "homepage": "https://inglorious-engine.vercel.app/",
13
13
  "bugs": {
14
- "url": "https://github.com/IngloriousCoderz/inglorious-engine/issues"
14
+ "url": "https://github.com/IngloriousCoderz/inglorious-forge/issues"
15
15
  },
16
16
  "keywords": [
17
17
  "state",
@@ -58,7 +58,7 @@
58
58
  "prettier": "^3.6.2",
59
59
  "vite": "^7.1.3",
60
60
  "vitest": "^1.6.1",
61
- "@inglorious/eslint-config": "1.1.0"
61
+ "@inglorious/eslint-config": "1.1.1"
62
62
  },
63
63
  "engines": {
64
64
  "node": ">= 22"