-
Notifications
You must be signed in to change notification settings - Fork 60
Add @rescript/runtime when finding bsc arguments #1125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Just 2 wishes for better types, and then a few smaller non-critical questions.
/** | ||
* Find all installed @rescript/runtime directories in the given project path. | ||
* In a perfect world, there should be exactly one. | ||
* This function is cached per project path. | ||
*/ | ||
export const findRescriptRuntimesInProject = findRuntimeCached(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this live together with the existing project state, or does it need to be on its own here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pulled this out so users can easily run the script and let us know if it finds the runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff! Let's release this as stable after the next beta release.
Proposed solution of rescript-lang/rescript#7858 (comment)
I extracted some code to find the bsc arguments as bsb/ninja and rewatch go there separate way there.