You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described in raquo/Laminar#91, Scala.js sjsir files contain the path & name of the original .scala file. My understanding is that these file names are then used to display the content of .scala files when debugging with source maps.
The problem for libraries is, by default the file paths in sjsir files are local to the machine on which the compilation happens, which is not the user machine where source maps are actually needed. The way to fix that is to use github URLs for raw files for file paths. I'd like to do that for Laminar and all of its dependencies, but the problem with tuplez is that it doesn't commit the generated .scala files to git, so there is nowhere we could point the source maps to.
To solve this, I propose that tuplez commits all of its generated files to git similar to how Airstream does it. I think it will be beneficial to users exploring the source code too. I'm not 100% sure about all the things you're generating but this approach seems like it should work. After you have the files, you need something like this in build.sbt:
Note: the js and shared paths are copy-pasta from scala dom types, you'll need something else depending on where you put the generated files. You can easily check that your .sjsir files link to the correct github URL.
The text was updated successfully, but these errors were encountered:
As described in raquo/Laminar#91, Scala.js sjsir files contain the path & name of the original .scala file. My understanding is that these file names are then used to display the content of .scala files when debugging with source maps.
The problem for libraries is, by default the file paths in sjsir files are local to the machine on which the compilation happens, which is not the user machine where source maps are actually needed. The way to fix that is to use github URLs for raw files for file paths. I'd like to do that for Laminar and all of its dependencies, but the problem with tuplez is that it doesn't commit the generated .scala files to git, so there is nowhere we could point the source maps to.
To solve this, I propose that tuplez commits all of its generated files to git similar to how Airstream does it. I think it will be beneficial to users exploring the source code too. I'm not 100% sure about all the things you're generating but this approach seems like it should work. After you have the files, you need something like this in build.sbt:
and this in turn requires
Note: the
js
andshared
paths are copy-pasta from scala dom types, you'll need something else depending on where you put the generated files. You can easily check that your .sjsir files link to the correct github URL.The text was updated successfully, but these errors were encountered: