ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #mithril
Learn how to diagnose and fix stale UI issues in Mithril.js caused by missing redraw cycles in external callbacks, timers, and WebSockets.
Learn how to bootstrap Mithril’s router with the fewest lines, manage dynamic route parameters, and protect navigation with lifecycle hooks and error handling. A practical guide for reliable single‑page applications.
When initializing a component's state in Mithril 2.x, developers must choose between the oninit and oncreate lifecycle hooks. The choice depends on whether the initialization logic requires access to the rendered DOM or must be completed before the first render cycle occurs. Using oninit allows for state setup before the virtual DOM is rendered, preventing p
I'm writing integration tests for a Mithril component that fetches JSON via m.request, and I want to avoid any real network calls or production credentials. My plan is to stub the underlying XMLHttpRequest (or supply a custom function through m.request's config) so the test resolves with a canned payload. The part I can't settle is error handling. When my mo
Developers want the request cache to stay fresh when users navigate between views, avoiding manual {cache: false} on every request. Currently Mithril’s m.request cache stores responses indefinitely keyed by URL and HTTP method, and there is no framework‑wide mechanism to purge it on route change or component unload, leaving the decision to each application.
m.request: Automatic Content-Type for non‑JSON payloads Mithril’s m.request automatically sets Content-Type: application/json when the payload is a plain JavaScript object and parses JSON responses. However, when the payload is a non‑JSON type such as FormData , Blob , or ArrayBuffer , the library sends the data without setting a Content-Type header, relying
Mithril.js provides m.request for declarative XHR and Fetch based data loading with custom headers, body and options supplied by application code. Routing via m.route supports parameterized paths and route resolvers that can load data before view rendering. The design goal is to render a large dataset with bounded queries and pagination while relying on core
I am planning an incremental migration of a small single-page application to Mithril (v2.x) without downtime. The goal is to use m.route and m.mount so that selected routes render new Mithril components while the rest of the page continues to be served by the existing legacy framework. The open uncertainty is how Mithril's redraw and lifecycle behavior inter
Mithril.js keeps views synchronized with state through an automatic redraw system that activates after DOM events and AJAX requests. When state changes occur outside those boundaries—inside setTimeout callbacks, WebSocket message handlers, or other external event listeners—developers commonly call m.redraw() to trigger reconciliation. The exact boundary wher
javascript