-
Notifications
You must be signed in to change notification settings - Fork 26
bisect_ppx is not marked as a dev dependency #26
Comments
I noticed that even if you put it in |
It needs to be part of bs-dependencies according to the bisect_ppx readme, that's also the case with the native side of things but I'm using buckleescript to generate the code coverage. |
If it needs to be part of I should mention, I asked about this in the #bucklescript channel, but I'd still be interested in hearing @aantron's feedback. |
This would be my suggestion. I'll submit a PR in about 10-12 hours (my AM). |
See rescript-lang/rescript#3761, also rescript-lang/rescript#3716 (comment). For now, the easiest thing to do is indeed to include The current alternative to listing |
Also cc @TheSpyder for suggesting a dev-only |
Ah my bad, I'll merge in the PR once it comes in |
Because this module is in the bsconfig `dependencies` list, it is required to be present for a successful build. Moving it to the npm `dependencies` will ensure that it is installed when `bs-bastet` is installed. resolves Risto-Stevcev#26
New relude depends on bs-bastet which depends on bisect_ppx which doesn't compile on Windows for me (in GitHub workflows). Relevant: Risto-Stevcev/bastet#26.
bisect_ppx
is a regular dependcy inbsconfig.json
, so depending code will not build until it has been been installed.The text was updated successfully, but these errors were encountered: