ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #purescript
PureScript’s Foreign Function Interface (FFI) lets you call JavaScript directly. This article walks through a real example, highlights common pitfalls, and shows how to keep your code safe and maintainable.
Learn how the PureScript bundle optimizer removes unused PureScript definitions, see a minimal example, and understand its limits and common pitfalls.
Learn how PureScript’s Effect monad uses row‑polymorphic types to track side‑effects, why you need explicit effect quantification for higher‑order functions, and how to verify your effect handling in practice.
Learn how to use PureScript Newtypes and Row Polymorphism to eliminate primitive obsession and enforce strict data boundaries using the 'Parse, don't validate' pattern.
Stop relying on fragile string concatenation for URLs. Learn how to use purescript-routing-duplex to create a bidirectional, type-safe routing system that catches broken links at compile time.
Learn how PureScript's row polymorphism enables flexible, structural typing for records, allowing functions to operate on data structures without rigid type definitions.
A concise guide to deriving FromJSON and ToJSON instances in PureScript using the purescript‑psa library, complete with a worked example, compile‑time safety, and common pitfalls.
PureScript employs row polymorphism to enable structural typing, allowing functions to operate on records containing a minimum set of required labels while preserving the remaining fields via row variables. A challenge arises when integrating these open rows within recursive type definitions. While row unification typically handles the inference of additiona
Integration goal Determine whether the PureScript FFI layer propagates JavaScript exceptions thrown inside a mock effect interpreter used with purescript-http-client as PureScript errors in the Effect monad, or whether such exceptions can terminate the test process. Constraints and uncertainty Tests must run without production credentials, using a pure mock