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
{{ message }}
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
When I start an Elm project, I usually put all Elm code in a src/ directory. When I run elm make src/Main.elm initially in a new project folder, I expect to find "source-directories": ["src"] in the newly created elm-package.json. But instead I have to add src/ manually every time. I have stumbled over this a couple of times and wondered why elm make doesn't find my other modules although they are in the same directory as Main.elm.
Wouldn't it be reasonable to add the relative path to the folder, that contains the main Elm module, to the newly created elm-package.json by default? Or would this break other use cases?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I start an Elm project, I usually put all Elm code in a
src/
directory. When I runelm make src/Main.elm
initially in a new project folder, I expect to find"source-directories": ["src"]
in the newly createdelm-package.json
. But instead I have to addsrc/
manually every time. I have stumbled over this a couple of times and wondered whyelm make
doesn't find my other modules although they are in the same directory asMain.elm
.Wouldn't it be reasonable to add the relative path to the folder, that contains the main Elm module, to the newly created
elm-package.json
by default? Or would this break other use cases?The text was updated successfully, but these errors were encountered: