ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
An architecture note describing how to use PureScript’s FFI to call JavaScript safely, covering requirements, minimal design, trust boundaries, checks, failure modes, and when to redesign.
Decide when to use raw PureScript FFI versus purescript-foreign boundary decoding for safer JavaScript interop.
Learn how Gleam's FFI interacts with the BEAM, the risks of the trust boundary between static and dynamic types, and how to verify external function signatures using Dialyzer.
PureScript's FFI lets you call JavaScript, but the compiler cannot see runtime shapes. Here is how to choose between direct bindings and purescript-foreign decoding.
Decide which PureScript FFI style to use when calling JavaScript, with a comparison table, trade-offs, and a validated spago workflow.
PureScript’s Foreign Function Interface lets you call JavaScript from pure code. This post walks through declaring imports, writing the JS side, bundling, and testing the boundary—plus the trade‑offs you should know.
Learn how to safely bridge PureScript and JavaScript using Maybe types and effect types to maintain type safety when calling foreign functions.
An architecture note on wrapping Erlang libraries from Gleam: private @external declarations, validating wrappers, tagged-tuple error contracts, and when to switch to OTP actors instead.
Step‑by‑step guide to diagnose and fix PureScript FFI runtime errors such as 'Foreign import failed' by checking annotations, exports, arity, and bundle inclusion.
purescript
erlang