Closed gnoff closed 8 years ago
also getting the same error, @gnoff beat me to opening basically the same issue
cc @yunxing I think the error is coming from installing jenga
Yeah consistently repros
Why did it previously work when you tested? Was it succeeding because jenga
was installed via opam or something?
@gnoff @anmonteiro Can you try the latest master? This is issue seems to be fixed.
@vramana yep, now installs. I would expect to find a rebel
executable in node_modules/.bin/
though, is this a wrong expectation?
We currently expect that you run eval $(dependencyEnv)
. This injects rebel binary into PATH. I haven't updated the Readme. So your npm script should look like this.
"scripts": {
"start": "eval $(dependencyEnv) && rebel"
}
@vramana Ok install works now.
unfortunately the start script does not. I get
> eval $(dependencyEnv) && rebel
sh: rebel: command not found
I tried running dependencyEnv directly and don't get any output so I don't think there is anything for me to eval
Can you show your package.json
?
Also, here's a new project we just made that will be running on CI so we know it has to work on a fresh machine. (Currently building for the first time, so if it passes, then you can just clone that project to get started) https://travis-ci.org/reasonml/RebelExampleProject
@jordwalke
{
"name": "helloreason",
"dependencies": {},
"scripts": {
"start": "eval $(dependencyEnv) && rebel",
"env": "dependencyEnv"
},
"rebel": {},
"devDependencies": {
"rebel": "github:reasonml/rebel"
}
}
the env
script was just to see if there was output from dependencyEnv
command run within the npm bin context.
I'd suggest using the RebelExampleProject
. Its tests run frequently, so it's known to work well. If that doesn't work, then we have a problem. npm install reasonml/rebel
isn't a tested installation method. Installing from package.json
that is already created (as the example project has) is tested/supported.
RebelExampleProject works like a charm. Thanks for the help
I commend your patience waiting for the compile times! We have a plan to (very soon) reduce it to about a third of what it is the first time, and to cache the artifacts for the second time you clone it as the basis for a project.
yeah, that install would be rough to do casually. Glad to hear it will get shorter soon.
@gnoff The problem in that config was using rebel as devDependency. It will work fine if it was a dependency.
@vramana created #64 to clear up possible confusion in readme.
It is HIGHLY likely this is user error but I don't know ocaml or reason (other than trying to get reason up and running and then trying to install this according to the instructions in the readme)
I followed the reasonml installation instructions here: https://github.com/facebook/reason/blob/master/README.md#install-stable
I was able to validate installation by compiling the Hello.re toy exampale at the end of the installation instructions
I then followed the installation instructions here: https://github.com/reasonml/rebel#for-consumers
Installation fails at inotify. I don't really know anything about ocamlfind but it also was not mentioned in the reason or rebel install instructions so I am assuming I don't have to know about it to get this installed.
Thanks, Josh