STON.fi Omniston Widget Offers Standalone TON Connect Mode for Lightweight dApps

·9 views

STON.fi's Omniston Widget supports a standalone TON Connect configuration that lets developers embed a swap widget with built-in wallet connectivity, without setting up a separate TON Connect instance. In this mode, the developer provides only a TON Connect manifest URL and a DOM mount point, while the widget handles all internal wallet connection logic. The setup suits landing pages, dashboards, and lightweight dApps where the swap widget is the primary feature requiring wallet access. However, standalone mode is not appropriate for applications that already manage their own TON Connect instance; those should use the integrated mode instead. Developers must host a publicly accessible TON Connect manifest file on the same domain as their application, following TON Connect requirements for HTTPS, open CORS policy, and raster image formats for the app icon.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer releases 'your-toast', a lightweight React and Next.js notification library

A developer has released your-toast, an open-source toast notification library designed for React and Next.js applications. The library features a glass-style UI and a minimal API, allowing developers to trigger success, error, warning, info, and loading notifications with a single function call. It includes a toast.promise() method that automatically handles loading, success, and error states tied to async operations. The library is architected around a central store and a provider component, removing the need for developers to manage notification state manually across components. A dedicated client-side entry point for Next.js App Router ensures the root layout can remain a Server Component without requiring a full client-side conversion.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

VRM Add-on Breaks on Blender 5.2 LTS and 5.3 Alpha Due to Exclusive Version Cap

Users upgrading to Blender 5.2 LTS or 5.3 alpha have found the VRM Addon for Blender failing to enable, with testing conducted on macOS Apple Silicon on September 22, 2026. The root cause is the blender_version_max field in the extension manifest, which marks the first unsupported Blender version rather than the last supported one — an exclusive upper bound. Add-on version 4.4.0 was the first release to declare a blender_version_max of 5.3.0, making it the minimum version that works on Blender 5.2 LTS; earlier extension versions such as 4.3.0 cap out at 5.1.x. A workaround exists for versions 4.3.0 and newer: installing the legacy add-on zip bypasses the version gate entirely, since it carries no manifest version restrictions. Version 3.9.0 fails on all paths under Blender 5.x because Blender 5.0 removed an API that the add-on imports.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a misconfigured 1.6 GB VPS froze for hours due to npm ci memory exhaustion

A developer's low-spec VPS running a static sleep-cycle calculator crashed twice in September — first for 10 hours on the 18th, then for 4 hours two days later — due to memory exhaustion triggered by running npm ci during deployments. Kernel logs confirmed the OOM killer terminated the npm process, which had consumed around 600 MB of real RAM on a machine with only 1,612 MB available and zero swap space configured. The combination of no swap and a vm.swappiness setting of 0 left the kernel no fallback mechanism, causing prolonged thrashing rather than a quick process kill. The developer resolved the issue by adding a 4 GB swapfile, adjusting vm.swappiness to 10, and installing earlyoom to trigger faster OOM kills before the system fully freezes. The post-mortem highlights that disabling swap entirely on memory-constrained servers can be more dangerous than the performance overhead it aims to avoid.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Spring Boot Explained: Key Features, Advantages, and Core Java Concepts

Spring Boot is a Java framework built on top of Spring that simplifies and accelerates application development by offering auto-configuration, embedded servers like Tomcat, and starter dependencies. Unlike traditional Spring, Spring Boot eliminates much of the boilerplate code and manual setup, making it well-suited for building web applications, REST APIs, and microservices. One of its key advantages over Spring is that applications can run independently without configuring a separate server. Java 8's Optional class complements such development by providing a safer way to handle null values, reducing the risk of NullPointerExceptions through methods like isPresent(). HTTP status codes also play a central role in these applications, as they are numeric responses from a server that inform clients whether a request succeeded, requires action, or resulted in an error.

0 comments Read more at DEV Community