Closed hugollm closed 8 years ago
My guess is that it has to do with Windows different directory separator .
Maybe, but on some underlying shit (express) package/middleware, i dont think it is run-js
problem - i mean, in first glance it looks good, it uses path
module which as i know dont have problems for such windows shits :D (note: damn, sorry for my aggressive ton, i hate windows ;d)
Cheers :beer: :)
Or the double slash thing (__bundle//
) setting here lib/routes/bundle-file.js#L19
Indeed I would prefer to be working on linux, but since I have to communicate with an C# API in a Windows project, It would be a pain to be switching between operational systems.
Since I bumped into this, I'm using prot for now. If I have the time, maybe I'll come back to this issue and try to solve it (since prot is not being actively maintained).
Thanks for catching this! This should be fixed with v2.1.0, which I've just published on npm. Let me know if you run into any other issues on Windows.
Works like a charm. Great Job!
Request for bundle fails under Windows when accessing root page (
/
).In this example I tried creating a simple
index.js
file and GET/
. When I tried to GET/index.js
it worked just fine. My guess is that it has to do with Windows different directory separator\
.