The source maps feature has been requested many times to the rescript team, however they do not see it as something necessary, at least not for now. Personally, I have not missed it that much (yet), because you can insert breakpoints in the generated .bs.js files.
Here are some threads on github and on rescript's blog talking about this topic:
Thanks to you @guilhermells
for taking the time to write this article!
Yeah, I'm watching those issues as well, imo, having the ability to debug is something than sooner or later you end up needing, sure, you can log to console to reduce a bit the pain but the experience is not the same.
This is not something exclusively of ReScript, I feel the same with Elixir that is hard to debug vs for example with TypeScript that with the sourcemaps the experience is the same as with vanilla JS.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi @mgtitimoli , thanks for your comment!
The source maps feature has been requested many times to the rescript team, however they do not see it as something necessary, at least not for now. Personally, I have not missed it that much (yet), because you can insert breakpoints in the generated .bs.js files.
Here are some threads on github and on rescript's blog talking about this topic:
Thanks to you @guilhermells for taking the time to write this article!
Yeah, I'm watching those issues as well, imo, having the ability to debug is something than sooner or later you end up needing, sure, you can log to console to reduce a bit the pain but the experience is not the same.
This is not something exclusively of ReScript, I feel the same with Elixir that is hard to debug vs for example with TypeScript that with the sourcemaps the experience is the same as with vanilla JS.