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
It would be great if a distribution of rationale could include the built js files within it.
The reason this would be useful is for publishing JS packages that depend on rescript code, if the built js files are included within the package, then the JS code can reference the built files within rationale, rather than needed to run rescript build -with-deps to create those dependencies (which can't be asked for when publishing a package).
The other alternative is include rationale inside the distribution of my package. However, I don't think that's ideal, as it leads to duplication. The rescript package itself follows the pattern of including js build files within its npm package.
It would be great if a distribution of rationale could include the built js files within it.
The reason this would be useful is for publishing JS packages that depend on rescript code, if the built js files are included within the package, then the JS code can reference the built files within rationale, rather than needed to run
rescript build -with-deps
to create those dependencies (which can't be asked for when publishing a package).The other alternative is include rationale inside the distribution of my package. However, I don't think that's ideal, as it leads to duplication. The rescript package itself follows the pattern of including js build files within its npm package.
For reference, a post on the forum about this issue: https://forum.rescript-lang.org/t/how-to-publish-a-rescript-project-for-javascript-users/656/9
And the original issue as it relates to my project: quantified-uncertainty/squiggle#42
The text was updated successfully, but these errors were encountered: