With regards to #261, node on windows is using back-slashes instead of forward-slashes when outputting file paths for the inline-cache. I explored applying a transform directly on the output after it had been stringified, but that seemed more risky than resolving on the client side (with default for *nix style forward-slashes) since there appear to be only 2 places the inline cache are retrieved there.
With regards to #261, node on windows is using back-slashes instead of forward-slashes when outputting file paths for the inline-cache. I explored applying a transform directly on the output after it had been stringified, but that seemed more risky than resolving on the client side (with default for *nix style forward-slashes) since there appear to be only 2 places the inline cache are retrieved there.