···226227 ([sobolevn](https://github.com/sobolevn))
228000000229- Generated code for the JavaScript target now includes a public API which can
230 be used for FFI interacting with Gleam custom types. For example, if you have
231 this Gleam code:
···226227 ([sobolevn](https://github.com/sobolevn))
228229+- The `erlang.application_start_argument` parameter has been added to
230+ `gleam.toml`. This is a string containing an Erlang term that will be written
231+ into the package's Erlang `.app` file if `erlang.application_start_module`
232+ has been set, replacing the default argument of `[]`.
233+ ([Louis Pilfold](https://github.com/lpil))
234+235- Generated code for the JavaScript target now includes a public API which can
236 be used for FFI interacting with Gleam custom types. For example, if you have
237 this Gleam code:
···708709#[derive(Deserialize, Serialize, Debug, PartialEq, Eq, Default, Clone)]
710pub struct ErlangConfig {
711+ /// An module that can be set in the `.app` file as the entrypoint for a stateful application
712+ /// that defines a singleton supervision tree.
713+ /// Erlang syntax.
714 #[serde(default)]
715 pub application_start_module: Option<EcoString>,
716+ /// The argument for the start module start function. If not set then `[]` is used as the
717+ /// default argument.
718+ /// Erlang syntax.
719+ #[serde(default)]
720+ pub application_start_argument: Option<EcoString>,
721 #[serde(default)]
722 pub extra_applications: Vec<EcoString>,
723}