Feature request: Option to nominate path of elm-stuff or configure it to be a hidden directory

[proehlen]

I can explain the use-case if you want me to but basically at the moment I'm forced to delete elm-stuff after every build which obviously slows down every subsequent re-build.

[proehlen]

Actually, I found I can get around the issue by hiding/un-hiding the directory in my build script. Feel free to close this issue if you think the feature isn't valuable.

#!/bin/bash
cd /Users/Peter/Git/clrflow/client/

# Unhide elm-stuff directory if it exists so elm-make doesn't redownload
# packages.
if [ -d ".elm-stuff" ]; then
  mv .elm-stuff elm-stuff
fi

elm make Main.elm --output=compatibility/clrflow.js --warn

# Hide elm-stuff so Meteor doesn't send the build javascript files
# to the client - they are only needed for/used by elm-make
mv elm-stuff .elm-stuff

[evancz]

Tracking from meta issue #98

[evancz]

I'm removing from the meta issue. I think we have generally decided that predictability is worth the trade offs.

• Having hidden directories can be really confusing. I personally hate having them secretly placed all over my computer.
• Having all Elm projects look basically the same is very valuable. If I can drop into a project and know exactly where everything will be, that can save me hours of wondering about stuff.

So on net, I think the value to specific expert users wanting to customize things is not worth the costs to other Elm users.