-
Hello and great project!
This is more of a help request than an issue, but I am trying to get coverage report to work when running tests via [bs-jest](https://github.com/glennsl/bs-jest).
Nothin…
-
WebpackError: It appears like Gatsby is misconfigured. Gatsby related `graphql` calls are supposed to only be evaluated at compile time, and then compiled away. Unfortunately, something went wrong a…
-
# 🐛 bug report
Running `--experimental-scope-hoisting` will fail to bundle an app claiming that an library is not exporting a file. I checked node modules to see if this was the case, but it's not. T…
-
moved from https://github.com/BuckleScript/bucklescript/issues/4327
Edit: can also repro on locally installed switch 4.09.0:
```
$ opam switch 4.09.0
$ time ocamlopt -w +A pattern.ml
Fatal erro…
-
# Fundraiser for Better Editor Support in Windows (Without WSL) #
## Why ##
Reason is still not at it's optimal support level in Windows because of shaky editor support.
Reason's VSCode extension…
-
**Original bug ID:** 7267
**Reporter:** @bobzhang
**Status:** acknowledged (set by @damiendoligez on 2016-09-27T14:12:28Z)
**Resolution:** open
**Priority:** normal
**Severity:** feature
**Target vers…
-
Hi!
I ran into some strange behaviour earlier today. Given the following type definition:
```reason
type segment = {
key: string,
title: string,
component: React.element,
};
```
And t…
-
Currently, this:
```reason
let f = (. x, y) => x + y;
let x = 1->f(. 2);
```
Does not work, with the error:
```
We've found a bug for you!
OCaml preview 2:15
This is an uncurried Buck…
-
It should be possible to call the odoc API directly instead of shelling out twice for every file in the project.
-
This is opinionated, but I think there's a wide agreement that more warnings is better.
[Here's one recommendation a lot of people follow:](https://dev.to/yawaramin/ocaml-reasonml-best-practice-wa…