Raoul Duke
2017-07-03 18:12:10 UTC
Is there very often a good reason to have more than one
elm-package.json in a project's tree, outside of elm-stuff/? If not,
it would perhaps be nice if elm-package warned me that I am trying to
(accidentally, duh) install packages in a subdir of a project that
already has a higher/top level elm-package.json, so that I don't then
have to spend more time cleaning up that accidental mess.
elm-package.json in a project's tree, outside of elm-stuff/? If not,
it would perhaps be nice if elm-package warned me that I am trying to
(accidentally, duh) install packages in a subdir of a project that
already has a higher/top level elm-package.json, so that I don't then
have to spend more time cleaning up that accidental mess.
--
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+***@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+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.