Skip to content

Cosictais@gmail.com #2299

Description

@raquelpn1979-tech

It looks like you are referring to the built JavaScript artifact (out.js) generated by the compilation of one of the example applications inside the Miso repository (a popular isomorphic front-end Haskell framework).
When you build a Miso application using GHCJS or WebAssembly, the Haskell code is compiled down into a standalone JavaScript bundle—often outputting to a path like Examples/miso/out.js or result/bin/app.jsexe/out.js.
Because out.js is the final compiled bundle, it consists of minified, optimized, or lower-level JavaScript (including the GHCJS runtime) rather than human-readable code.
If you are trying to view, edit, or understand what that specific example is doing, you'll want to look at the Haskell source files rather than the generated out.js.

Where to look instead:

  1. Main.hs: The core entry point where the Miso application structure is defined. Look for functions like startApp, miso, or App configurations.
  2. The App Architecture: Miso strictly follows the Elm Architecture. In the source files, you'll be able to easily read the code split into:
  • Model: The data structure representing your application state.
  • Action: An algebraic data type (ADT) representing everything that can happen in your app.
  • Update: A pure function describing how an Action transforms the old Model into a new one.
  • View: The user interface layout, written in type-safe Haskell functions that mirror HTML tags (like div_, button_, etc.).
    If you meant to paste the contents of out.js or have a specific issue running/building this example, let me know! What exactly are you trying to do with this example?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions