melange: find out js artifact of a given ml source
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
Dune and Melange default to placing .js artifacts in _build folder. In comparison, ReScript default behavior is to put .js artifacts next to the sources.
To help Melange users look at the resulting .js files, it would be nice to have the ability to "Inspect JavaScript output" from editors. To do so, Dune could look up all the melange.emit stanzas in the workspace and search for the given module emitted in them. Then editor tooling libraries could consume this functionality through rpc.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Dune discovers and processes melange.emit stanzas in a workspace. The work is done when a given Melange source module can be mapped to its emitted JavaScript artifact and the lookup is consumable by editor tooling through RPC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100