memorio 4.3.5 → 4.5.0

package/markdown/CHANGELOG.md

@@ -56,7 +56,7 @@ All notable changes to this project will be documented in this file.
 
 ### 📝 Documentation Updates
 
-- `docs/README.md`: replaced `console.log` with `console.debug` in usage examples; fixed `esbuild` badge → `tsup`
+- `docs/README.md`: replaced `console.debug` with `console.debug` in usage examples; fixed `esbuild` badge → `tsup`
 - `.github/CHANGELOG.md`: restructured with fix / security / changed sections
 - `.github/HISTORY.md`: complete rewrite through v3.0.2
 - `.github/SECURITY.md`: NIST/NSA standard + OWASP Top 10 mapping

package/markdown/DISPATCH.md

@@ -0,0 +1,168 @@
+# Dispatch - Memorio
+
+> ⚛️ **Vanilla JS**: This is for non-React applications. For React, use [`useObserver`](USEOBSERVER.md).
+
+`memorio.dispatch` is an event system for vanilla JavaScript applications. It enables pub/sub patterns without React hooks.
+
+## Installation
+
+```bash
+npm install memorio
+```
+
+```javascript
+import 'memorio';
+```
+
+---
+
+## Quick Examples
+
+### Example 1: Basic Event Listening
+
+```javascript
+// Listen for an event
+memorio.dispatch.listen('my:event', (event) => {
+  console.debug('Event triggered:', event.detail);
+});
+
+// Trigger the event
+memorio.dispatch.set('my:event', { detail: { data: 'Hello World' } });
+// Output: "Event triggered: { data: 'Hello World' }"
+```
+
+### Example 2: State Reactivity (Vanilla JS)
+
+```javascript
+// React to state changes without React
+memorio.dispatch.listen('state.counter', (event) => {
+  console.debug('Counter is now:', event.detail);
+});
+
+// Update state
+state.counter = 1;
+// Output: "Counter is now: 1"
+
+state.counter = 5;
+// Output: "Counter is now: 5"
+```
+
+### Example 3: Remove Listener
+
+```javascript
+// Remove a specific event listener
+memorio.dispatch.remove('my:event');
+
+// Or remove all listeners for state changes
+memorio.dispatch.remove('state.user');
+```
+
+---
+
+## API Reference
+
+### memorio.dispatch.set(name, value)
+
+Dispatches a custom event with the specified name and value.
+
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `name` | `string` | Event name (e.g., `'my:event'`, `'state.counter'`) |
+| `value` | `object` | Object with `detail` property (default: `{}`) |
+
+```javascript
+memorio.dispatch.set('custom:event', { detail: { data: 'value' } });
+```
+
+### memorio.dispatch.listen(name, callback)
+
+Listens for the specified event and executes the callback when triggered.
+
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `name` | `string` | Event name to listen for |
+| `callback` | `function` | Function called with the event object |
+
+```javascript
+memorio.dispatch.listen('state.user', (event) => {
+  console.debug('User changed:', event.detail);
+});
+```
+
+### memorio.dispatch.remove(name)
+
+Removes the event listener for the specified event name.
+
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `name` | `string` | Event name to stop listening |
+
+```javascript
+memorio.dispatch.remove('state.counter');
+```
+
+---
+
+## Common Patterns
+
+### Form Validation
+
+```javascript
+memorio.dispatch.listen('state.form.email', (event) => {
+  const email = event.detail;
+  const isValid = email.includes('@');
+  state.form.isValid = isValid;
+});
+```
+
+### Analytics Tracking
+
+```javascript
+memorio.dispatch.listen('state.page', (event) => {
+  const page = event.detail;
+  analytics.track('page_view', { page });
+});
+```
+
+### Auto-save
+
+```javascript
+memorio.dispatch.listen('state.draft', (event) => {
+  const content = event.detail;
+  store.set('autosave', content);
+});
+```
+
+### Multiple Listeners
+
+```javascript
+// Listen for multiple state changes
+memorio.dispatch.listen('state.user', (e) => console.log('User:', e.detail));
+memorio.dispatch.listen('state.settings', (e) => console.log('Settings:', e.detail));
+```
+
+---
+
+## Migration from observer()
+
+The `observer()` Replace it with `memorio.dispatch.listen()`:
+
+```javascript
+observer('state.counter', (newValue) => {
+  console.debug('Counter:', newValue);
+});
+
+// NEW (recommended for vanilla JS)
+memorio.dispatch.listen('state.counter', (event) => {
+  console.debug('Counter:', event.detail);
+});
+```
+
+---
+
+## Best Practices
+
+1. Use specific event names: `'state.user.name'` not `'state'`
+2. Clean up listeners when no longer needed with `memorio.dispatch.remove()`
+3. Use `event.detail` to access the value
+4. For React applications, use [`useObserver`](USEOBSERVER.md) instead

package/markdown/OBSERVER.md

@@ -1,7 +1,5 @@
 # Observer - Memorio
 
-> ⚠️ **DEPRECATED**: This function is deprecated and will be removed in future versions. Please use [`useObserver`](USEOBSERVER.md) instead.
-
 Observer lets you react to state changes. When a state key changes, your callback function runs.
 
 ## Installation
@@ -21,9 +19,6 @@ import 'memorio';
 ### Example 1: Basic Usage
 
 ```javascript
-// Simple observer (DEPRECATED - use useObserver instead)
-console.warn('observer() is deprecated. Please use useObserver() for React or memorio.dispatch for vanilla JS.');
-
 observer('state.counter', (newValue) => {
   console.debug('Counter is now:', newValue);
 });
@@ -35,8 +30,6 @@ state.counter = 5;
 // Output: "Counter is now: 5"
 ```
 
-> **Note**: For new projects, use [`useObserver`](USEOBSERVER.md) for React or [`memorio.dispatch`](SUMMARY.md) for vanilla JS.
-
 ### Example 2: Intermediate
 
 ```javascript
@@ -55,9 +48,8 @@ state.user = { name: 'Luigi' };
 ### Example 3: Advanced
 
 ```javascript
-// Multiple observers
-const obs1 = observer('state.data', handler1);
-const obs2 = observer('state.data', handler2);
+// Multiple callbacks for same path
+observer('state.data', [handler1, handler2]);
 
 // List all observers
 console.debug(observer.list);
@@ -68,18 +60,45 @@ observer.remove('state.data');
 
 // Remove all observers
 observer.removeAll();
+
+// Check if observer exists
+if (observer.has('state.counter')) {
+  console.debug('Observer exists for counter');
+}
+```
+
+---
+
+## Direct Values (Vanilla JS)
+
+Observer supports direct state values, not just string paths:
+
+```javascript
+// Direct value - no string needed!
+observer(state.counter, (newValue) => {
+  console.debug('Counter:', newValue);
+});
+
+// Works with objects too
+observer(state.user, (newValue) => {
+  console.debug('User:', newValue?.name);
+});
+
+// Multiple callbacks as array
+observer('state.data', [cb1, cb2, cb3]);
 ```
 
 ---
 
 ## API Reference
 
-### observer(path, callback)
+### observer(path, callback, option)
 
 | Parameter | Type | Description |
 |-----------|------|-------------|
-| `path` | `string` | State path to watch (e.g., `'state.counter'`) |
-| `callback` | `function` | Function called on change |
+| `path` | `string \| object` | State path (e.g., `'state.counter'`) or direct state value |
+| `callback` | `function \| array` | Function(s) called on change. Can be a single function or array of functions |
+| `option` | `boolean` | Listen continuously (default: `true`) |
 
 ### Callback Parameters
 
@@ -102,6 +121,7 @@ observer('state.key', (newValue, oldValue) => {
 |--------|------------|-------------|
 | `observer.remove(name)` | `string` | Remove observer for specific path |
 | `observer.removeAll()` | none | Remove all observers |
+| `observer.has(name)` | `string` | Check if observer exists for path (returns boolean) |
 
 ---
 

package/markdown/USEOBSERVER.md

@@ -24,6 +24,7 @@ import 'memorio';
 import 'memorio';
 
 function Counter() {
+  // Direct values work! ✅
   useObserver(() => {
     console.debug('Counter changed:', state.counter);
   }, [state.counter]);
@@ -63,14 +64,23 @@ function UserProfile() {
 ### Example 3: Advanced
 
 ```javascript
-// Multiple watchers with array
+// Multiple watchers with array - works with direct values
 function MultiWatch() {
   useObserver(() => {
     console.debug('A or B changed:', state.a, state.b);
-  }, [state.a, state.b]);
-
+  }, [state.a, state.b]); // Direct values work!
+  
   return <div>{state.a} - {state.b}</div>;
 }
+
+// With string path (for store)
+function StoreWatcher() {
+  useObserver(() => {
+    console.debug('Store changed');
+  }, 'store.userPreferences');
+
+  return <div />;
+}
 ```
 // With string path (for store)
 function StoreWatcher() {
@@ -91,15 +101,49 @@ function StoreWatcher() {
 | Parameter | Type | Description |
 | --------- | ---- | ----------- |
 | `callback` | `function` | Function to run on change |
-| `deps` | `function \| string \| array` | State path(s) to watch |
+| `deps` | `function \| string \| array \| proxy` | State path(s) to watch. Supports: |
+| | | - Direct values: `state.counter` |
+| | | - String paths: `'state.counter'` |
+| | | - Arrow functions: `() => state.counter` |
+| | | - Arrays: `[state.a, state.b]` or `['state.a', 'state.b']` |
+| | | - Optional chaining: `[state?.one]` |
+
+### Primitive Values
+
+Direct primitive values are now fully supported:
+
+```javascript
+// Direct values work with primitives ✅
+useObserver(() => { console.debug('changed') }, [state.counter])
+
+// Arrays of primitives work ✅
+useObserver(() => { console.log(state.a, state.b) }, [state.a, state.b])
+
+// Optional chaining works ✅
+useObserver(() => { console.log(state?.one) }, [state?.one])
+
+// Strings still work ✅
+useObserver(() => { console.debug('changed') }, ['state.counter'])
+
+// Functions still work ✅
+useObserver(() => { console.debug('changed') }, [() => state.counter])
+```
 
 ### Callback Parameters
 
 ```javascript
+// Single value (no array needed)
 useObserver(
   () => {
     console.debug('Changed:', state.key);
-  }, [state.key]
+  }, state.key  // Single value works!
+);
+
+// Array of values
+useObserver(
+  () => {
+    console.debug('Changed:', state.key);
+  }, [state.key]  // Array also works!
 );
 ```
 
@@ -129,24 +173,79 @@ Returns a cleanup function:
 
 ## Common Patterns
 
-### Sync with useState
+### Sync with useState (Recommended for Primitives)
 
 ```javascript
-function MyComponent() {
-  const [data, setData] = useState(null);
+function CounterComponent() {
+  // Sync memorio state with React state
+  const [counter, setCounter] = useState(state.counter)
+  
+  // React useEffect works correctly with primitive values
+  useEffect(() => {
+    console.log('Counter changed:', counter)
+  }, [counter])
+  
+  // Direct values now work with primitives!
+  useObserver(() => {
+    setCounter(state.counter)
+  }, [state.counter])  // ✅ Works now!
+  
+  return (
+    <div>
+      <button onClick={() => { state.counter++ }}>Increment</button>
+      <span>{counter}</span>
+    </div>
+  )
+}
+```
 
-  useObserver((newVal) => {
-    setData(newVal);
-  }, [state.data]);
+### Safe Access with Optional Chaining (Protection)
 
-  return <div>{data}</div>;
+```javascript
+// Optional chaining is supported - protects against errors
+useObserver(() => {
+  if (test?.one) {
+    console.log(test.one)
+  }
+}, [test?.one])
+
+// Works with objects
+function SafeComponent() {
+  const [test, setTest] = useState(state.test)
+  
+  useEffect(() => {
+    if (test?.one) {
+      console.log('test.one:', test.one)
+    }
+  }, [test?.one])
+  
+  useObserver(() => {
+    if (state.test?.one) {
+      setTest(state.test)
+    }
+  }, ['state.test.one'])
+  
+  return <div>{test?.one || 'Loading...'}</div>
 }
 ```
 
 ### Multiple Watchers
 
 ```javascript
-}, [state.a, state.b]);
+// Watch multiple properties with strings
+useObserver(() => {
+  console.log(state.a, state.b)
+}, ['state.a', 'state.b'])
+
+// Watch multiple properties with functions
+useObserver(() => {
+  console.log(state.a, state.b)
+}, [() => state.a, () => state.b])
+
+// Watch with auto-discovery
+useObserver(() => {
+  console.log(state.a, state.b) // Automatically tracks both
+}, [])
 ```
 
 ---

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "memorio",
   "codeName": "memorio",
-  "version": "4.3.5",
+  "version": "4.5.0",
   "description": "Memorio, State + Observer, Store and iDB for an easy life - Cross-platform compatible",
   "main": "./index.cjs",
   "browser": "./index.cjs",

package/types/memorio.d.ts

@@ -29,6 +29,9 @@ interface _memorio {
   _tracking?: boolean
   _trackedPaths?: Set<string>
   _locked?: boolean
+  _lastAccessedPath?: string
+  _stateVersion?: number
+  _propertyAccessLog?: string[]
   // Platform detection
   isBrowser: () => boolean
   isNode: () => boolean

package/types/store.d.ts

@@ -13,7 +13,7 @@ interface _store {
      * @param name The String as name to define the store.
      * @param value The information you want to store. Functions are blocked for security.
      * @return void
-     */
+     */
   set: (name: string, value: any) => void
 
   /**

package/CODE_OF_CONDUCT.md

@@ -1,108 +0,0 @@
-# Code of Conduct — memorio
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to make participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate,
-threatening, offensive, or harmful.
-
-Project maintainers have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will
-communicate reasons for moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at <dariopassariello@gmail.com>.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.

package/CONTRIBUTING.md

@@ -1,105 +0,0 @@
-# Contributing
-
-First off, thanks for taking the time to contribute!
-
-All types of contributions are encouraged and valued. See the [Table of Contents](contributing.md#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions.
-
-> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
->
-> * Star the project
-> * Tweet about it
-> * Refer this project in your project's readme
-> * Mention the project at local meetups and tell your friends/colleagues
-
-## Table of Contents
-
-* [Code of Conduct](contributing.md#code-of-conduct)
-* [I Have a Question](contributing.md#i-have-a-question)
-  * [I Want To Contribute](contributing.md#i-want-to-contribute)
-  * [Reporting Bugs](contributing.md#reporting-bugs)
-  * [Suggesting Enhancements](contributing.md#suggesting-enhancements)
-  * [Your First Code Contribution](contributing.md#your-first-code-contribution)
-  * [Improving The Documentation](contributing.md#improving-the-documentation)
-* [Style guides](contributing.md#styleguides)
-  * [Commit Messages](contributing.md#commit-messages)
-* [Join The Project Team](contributing.md#join-the-project-team)
-
-## Code of Conduct
-
-This project and everyone participating in it is governed by the [memorio Code of Conduct](https://github.com/picla-net/picla.npm.memorio/blob/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [dariopassariello@gmail.com](mailto:dariopassariello@gmail.com).
-
-## I Have a Question
-
-Before you ask a question, it is best to search for existing [Issues](https://github.com/picla-net/picla.npm.memorio/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
-
-If you then still feel the need to ask a question and need clarification, we recommend the following:
-
-* Open an [Issue](https://github.com/picla-net/picla.npm.memorio/issues/new).
-* Provide as much context as you can about what you're running into.
-* Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
-
-We will then take care of the issue as soon as possible.
-
-## I Want To Contribute
-
-> ### Legal Notice
->
-> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
-
-### Reporting Bugs
-
-#### Before Submitting a Bug Report
-
-A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
-
-* Make sure that you are using the latest version.
-* Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment
-* To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/picla-net/picla.npm.memorio/issues?q=label%3Abug).
-* Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
-* Collect information about the bug:
-  * Stack trace (Traceback)
-  * OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
-  * Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
-  * Possibly your input and the output
-  * Can you reliably reproduce the issue? And can you also reproduce it with older versions?
-
-#### How Do I Submit a Good Bug Report?
-
-> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to [dariopassariello@gmail.com](mailto:dariopassariello@gmail.com).
-
-We use GitHub issues to track bugs and errors. If you run into an issue with the project:
-
-* Open an [Issue](https://github.com/picla-net/picla.npm.memorio/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
-* Explain the behavior you would expect and the actual behavior.
-* Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
-* Provide the information you collected in the previous section.
-
-Once it's filed:
-
-* The project team will label the issue accordingly.
-* A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
-* If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](contributing.md#your-first-code-contribution).
-
-### Suggesting Enhancements
-
-This section guides you through submitting an enhancement suggestion for memorio, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
-
-#### Before Submitting an Enhancement
-
-* Make sure that you are using the latest version.
-* Perform a [search](https://github.com/picla-net/picla.npm.memorio/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
-* Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
-
-#### How Do I Submit a Good Enhancement Suggestion?
-
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/picla-net/picla.npm.memorio/issues).
-
-* Use a **clear and descriptive title** for the issue to identify the suggestion.
-* Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
-* **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
-* You may want to **include screenshots or screen recordings** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [screentogif](https://www.screentogif.com/) to record GIFs on macOS and Windows, and the built-in [screen recorder in GNOME](https://help.gnome.org/users/gnome-help/stable/screen-shot-record.html.en) or [SimpleScreenRecorder](https://github.com/MaartenBaert/ssr) on Linux.
-* **Explain why this enhancement would be useful** to most boilerplate users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
-
-## Join The Project Team
-
-Please send email to <dariopassariello@gmail.com>