ng-prism offers Angular-native Storybook alternative with compiler-driven docs

·3 views

A developer has released ng-prism, an Angular-native component showcase tool designed as an alternative to Storybook for Angular component libraries. Unlike Storybook, ng-prism uses a single @Showcase decorator placed directly on the component, with the TypeScript Compiler API extracting metadata at build time rather than relying on separate story files or runtime reflection. The tool renders components directly into the document instead of an iframe, avoiding isolation issues with Angular CDK overlays and portal-based elements like MatDialog. Version 22.2 ships with three new features: a visual-regression panel, an Overview contact sheet, and a redesigned UI built around a density scalar. Setup requires one command that integrates ng-prism's builders into an existing angular.json, and a provided transformer strips the decorator from compiled output so end users of published libraries need not install ng-prism.

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)

Amblyotube Uses Meta Quest VR to Treat Lazy Eye Through YouTube Viewing

Amblyotube is a Meta Quest application designed to treat amblyopia, commonly known as lazy eye, by delivering tailored visual stimuli to each eye while users watch YouTube content. The app uses AI-driven shaders to sharpen input for the weaker eye and reduce dominance of the stronger eye, encouraging the brain to integrate signals from both. Users can adjust settings such as opacity, blur, contrast, and brightness through an in-headset control panel, though accurate configuration is flagged as critical to avoid worsening imbalances. A controlled flicker effect highlights human figures in video content to keep the lazy eye engaged, mimicking therapeutic repetition within everyday entertainment. The project is currently open for developer review, with a public APK available through Seven Sports' developer portal.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Rails Has Quirky Ordinal Methods Up to .forty_two for Array Access

Ruby on Rails includes a set of unconventional helper methods that allow developers to access collection elements by ordinal position. These methods include .second, .third, .fourth, and .fifth, and unusually extend all the way to .forty_two. The inclusion of .forty_two is widely regarded as a nod to the number 42, famously referenced in Douglas Adams' 'The Hitchhiker's Guide to the Galaxy' as the answer to life, the universe, and everything. These convenience methods are part of Rails' ActiveSupport library and serve as readable shortcuts for index-based access. The quirky addition reflects the Rails community's tradition of blending practicality with developer humor.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Ethereum-Like Blockchain From Scratch in C++17 With No External Libraries

Developer Martial Zinsou has released Nstrike version 0.1.0, an open-source MVP implementation of an Ethereum-style blockchain written entirely in modern C++17. The project was built from scratch without any external dependencies such as OpenSSL, Boost, or secp256k1, with all cryptographic primitives implemented manually. Nstrike includes a mini virtual machine, ERC-20 token support, Proof-of-Work consensus, a JSON-RPC 2.0 server, and a command-line wallet interface. The codebase passes a suite of 32 unit and integration tests covering SHA-256, Keccak-256, ECDSA, and 256-bit arithmetic. Published under the MIT licence, the project is compatible with macOS and Linux and is available on GitHub.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build a Production-Ready Polymarket Trading Bot in Rust

Developer Bo$onaX has published a detailed architectural guide for building a production-grade trading bot on Polymarket, the decentralized prediction market platform. The design separates six core layers — market discovery, data ingestion, strategy engine, risk controls, execution, and reconciliation — to handle asynchronous state changes reliably. A key principle is that a successful HTTP response should never be assumed to confirm correct trading state, so order and fill events feed back into state and risk systems via a dedicated reconciliation loop. The guide recommends using Rust, WebSocket streams for low-latency market data, and fixed-point arithmetic instead of floating-point for price and size calculations. Strategy decisions are expressed as structured OrderIntent objects, keeping strategy logic, risk validation, and order execution cleanly isolated from one another.

0 comments Read more at DEV Community