3 ms·

Installation is broken with bs-platform, do this to fix it (assuming node is installed in /home/pc/node) rm /home/pc/node/lib/node_modules/bs-platform/bin/refm

by napa15 9y ago

Installation is broken with bs-platform, do this to fix it (assuming node is installed in /home/pc/node) rm /home/pc/node/lib/node_modules/bs-platform/bin/refmt.exe ln -s /home/pc/node/bin/refmt /home/pc/node/lib/node_modules/bs-platform/bin/refmt.exe Is there no source map support? Also: I have to set up requirejs myself to make Reason code work in the browser? Not only that, it doesnt seem like the whole "each file is a module" system is actually codified in the output. I see no require calls that would indicate the right loading order for my generated .js files. Generated code has weird comments in it like /* Facebook / and / Instagram */

napa15 9y ago
the bs-loader is definitely broken somehow, it only picks up the entry .re file and not any of the other files, I even tried the example from the bs-loader (which is still reason 2 btw)
yawaramin 9y ago
There is no source map support because the output JS should correspond almost 1-1 with the input Reason. Can you give an example of 'I see no require calls'? Require or import calls should be generated correctly.
- napa15 9y ago
  I dont know what to tell you, I'm using the simplest possible project here. It just doesnt seem to pick up anything other than the entry.re file. I initially only had the non-webpack default compilation set up, which does compile all .re files but has the problem that the modules dont get loaded / no idea which order should be loaded. So naturally I set up webpack but now it only watches the entry.re file for some reason. And saying that the output js corresponds 1-1 with reason is really not true at all, especially when compiled into one big module with webpack. https://i.imgur.com/hrxmjWl.png https://i.imgur.com/hrxmjWl.png
  - yawaramin 9y ago
    I think it only watches one of your files because the other one isn't actually referenced by any code in the pathway of your entry point. If you reference some code from your other file, it will be picked up as well. Yes, I forgot about bundling, sorry, but if you are in debug mode you're not minifying the bundle JS anyway so whatever you're looking at should still look a fair bit like the input Reason, especially because the names are only minimally mangled.

by napa15 9y ago

napa15 9y ago

the bs-loader is definitely broken somehow, it only picks up the entry .re file and not any of the other files, I even tried the example from the bs-loader (which is still reason 2 btw)

yawaramin 9y ago

There is no source map support because the output JS should correspond almost 1-1 with the input Reason. Can you give an example of 'I see no require calls'? Require or import calls should be generated correctly.

napa15 9y ago
I dont know what to tell you, I'm using the simplest possible project here. It just doesnt seem to pick up anything other than the entry.re file. I initially only had the non-webpack default compilation set up, which does compile all .re files but has the problem that the modules dont get loaded / no idea which order should be loaded. So naturally I set up webpack but now it only watches the entry.re file for some reason. And saying that the output js corresponds 1-1 with reason is really not true at all, especially when compiled into one big module with webpack. https://i.imgur.com/hrxmjWl.png https://i.imgur.com/hrxmjWl.png
- yawaramin 9y ago
  I think it only watches one of your files because the other one isn't actually referenced by any code in the pathway of your entry point. If you reference some code from your other file, it will be picked up as well. Yes, I forgot about bundling, sorry, but if you are in debug mode you're not minifying the bundle JS anyway so whatever you're looking at should still look a fair bit like the input Reason, especially because the names are only minimally mangled.