-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support Elm 0.19 #8
Conversation
@Punie I have opened a PR in your fork that also fixes the tests for this branch: https://github.com/Punie/find-elm-dependencies/pull/1 |
@hecrj Thank you ! I merged it just now :) |
function getElmPackageSourceDirectories(baseDir, currentDir) { | ||
if (typeof currentDir === "undefined") { | ||
baseDir = path.resolve(baseDir); | ||
currentDir = baseDir; | ||
} | ||
|
||
var elmPackagePath = path.join(currentDir, 'elm-package.json'); | ||
var elmPackagePath = path.join(currentDir, 'elm.json'); |
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.
Not really elmPackagePath
anymore, isn't it more like elmJsonPath
?
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 guess it's still the file that defines the packages on which the elm build depends.
I'm happy to make the change to elmJsonPath
if this terminology seems more sensible :)
Looks good to me. @stoeffel / @rtfeldman can you merge and release? |
Hi !
I made a small change to support Elm 0.19 (by locating
elm.json
instead ofelm-package.json
).As far as I know, other than this filename change, there were no fundamental differences on how modules and imports are resolved in 0.19.
This upgrade is necessary for
node-elm-compiler
andelm-webpack-loader
to support Elm 0.19 (PR #142 on elm-webpack-loader)