Closed kflu closed 9 years ago
I just ran into the same problem.
Can you show me hi2.iced
? Which version of iced are you running?
After a recent refactor (around 1.7.1-e), there is a difference between base CoffeeScript and Iced, in that iced needs access to an external library, called iced-runtime
, which can be installed separately. The reason I did this is that the compiler was getting pretty bloated in terms of dependencies. I didn't want to force people using the output of iced --compile
to install iced-coffee-script
; rather, they can just use iced-runtime
instead, which has way fewer dependencies.
To see an example of this approach in action, check out something like the keybase node client. iced-coffee-script
is a devDependency if you want to build the thing yourself, but if you just want to run it, iced-runtime
is a dependency.
same problem here.
I thought a little about this, my guess is that there's a version mismatch. You have an old and new version of iced installed, and your shell is finding the old version, while your library path is set to the new version. The new versions (v1.7.1-c and above) include 'iced-runtime', while the old version includes 'iced-coffee-script'.
I think I figured it out. Should be closed in v1.7.1-g (01dd7d47a7058ebc0865184e8bc4431cd6cb1a1f). Give it a whirl
I've got the following error:
The fix is similar to this issue by setting NODE_PATH. What's weird is that I install coffee and iced the same way, both live in the same globally node_module. But:
Why is that? Could setup take care of that. I can also confirm coffee works without setting
NODE_PATH
. I'm using Windows 8 x64 bit. Both coffee and iced were installed using npm with-g
.