To expand on what simon said: If you're using multiple Elm versions in production, use the version installed via a local npm and make all your tooling refer to node_modules/.bin/elm-make and friends. That way you can have a global install of elm at a version, but still use 0.16 for a particular project
On Wed, Nov 30, 2016 at 8:56 PM, Mickey Vashchinsky <mickey....@gmail.com> wrote: > Maybe this would be helpfull: > > https://www.npmjs.com/package/elm-version-manager > > > On Tuesday, November 29, 2016 at 3:54:06 PM UTC+2, Rupert Smith wrote: >> >> I've been trying to follow these instructions: >> >> http://www.lambdacat.com/how-to-setup-local-development-for-elm/ >> >> but getting some errors when trying to build from source. >> >> Is there an easier way? I don't want to blat my exising 0.17 with 0.18 >> right away, would rather keep it around until I have finished upgrading. >> >> Perhaps just create a vm or docker container and install elm 0.18 inside >> that? > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elm-discuss+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
