Replies: 4 comments 6 replies
-
|
Hi @nojaf , regarding
AFAIK, jihchi/vite-plugin-rescript does not write files to disk. Could you please elaborate on that? What the plugin does is to simply spawn a process of the ReScript compiler in the background and redirect error logs from the |
Beta Was this translation helpful? Give feedback.
-
Sure, if I have a |
Beta Was this translation helpful? Give feedback.
-
Sorry, I don't get your expectation in this scenario. You'd get the same result without using the plugin. In other words, you'd get the same result by just executing |
Beta Was this translation helpful? Give feedback.
-
|
Yes, which is why I'm opening this discussion on the compiler side. In my naive mindset, any imports to a |
Beta Was this translation helpful? Give feedback.
-
|
Got it! Thank you for the explanation. |
Beta Was this translation helpful? Give feedback.
-
|
There are two issues:
|
Beta Was this translation helpful? Give feedback.
-
|
Where would |
Beta Was this translation helpful? Give feedback.
-
|
So, I just saw the intro to the compiler by @cristianoc. Running If my hunch is correct, where could I find where |
Beta Was this translation helpful? Give feedback.
-
|
It's a bit more involved than that, the build system (either rescript.exe or rewatch) also decides when to rebuild/what to cache. In a naive approach you would probably just rebuild everything. Regardless, here's an example where we call the compiler directly for the docs example tests: https://github.com/rescript-association/rescript-lang.org/blob/master/scripts/test-examples.mjs#L98-L115 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, good point. I would basically want to spin up rewatch in some process and keep it running. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
As someone new to ReScript, I'm trying to find an optimal integration with Vite. The current approaches are either to run a separate terminal or to use jihchi/vite-plugin-rescript.
Running a separate terminal is less than ideal. The
vite-plugin-rescriptapproach, which writes files to disk, poses its own problems. For instance, if there's an error in the ReScript code, the plugin might resort to using an outdated file, leading to confusion and loss of React state.I'm curious about the feasibility of compiling ReScript code in-memory to address these issues. Such a method would ensure the Vite plugin always has access to the latest version of the code and might also enhance performance by reducing I/O operations.
I've initiated this discussion as I'm unsure if in-memory compilation is currently feasible with ReScript. I'm open to being corrected on this.
I'm also curious if you considered this @jihchi?
Beta Was this translation helpful? Give feedback.
All reactions