-
Notifications
You must be signed in to change notification settings - Fork 43
Add a way to look up where the elm binaries are #64
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
base: master
Are you sure you want to change the base?
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.
Looks great!
we should use this in |
Yeah I thought we did already but I was wrong |
module.exports = { | ||
compile: compile, | ||
compileSync: compileSync, | ||
compileWorker: require("./worker.js")(compile), | ||
compileToString: compileToString, | ||
compileToStringSync: compileToStringSync, | ||
findAllDependencies: findAllDependencies | ||
findAllDependencies: findAllDependencies, | ||
findElmBinaries: findElmBinaries |
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.
Maybe this name is bad?
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.
how about preferedElmBinaries
or elmBinariesLocation
?
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.
Yeah, based on the name I'd be surprised to learn this was searching node_modules
first... 🤔
That said, I haven't thought of a better one. 😅
This is used in a few projects, like:
Likewise, it should probably be used in elm-webpack-loader and similar tools, since generally the expected behaviour for these tools is to use the locally installed (node_modules) over the global