Closed thatguyhampton closed 8 years ago
I took a look at elms way of compiling things and the library only gets compiled into my generated javascript file when it is imported. So for this reason I should be able to have just a single elm-package.json file with all of the shared dependencies because the unused ones will not affect the file size of the resulting compiled javascript files. So basically Hodor... and no fix needed. :)
Glad you worked it out On May 8, 2016 03:32, "thatguyhampton" notifications@github.com wrote:
I took a look at elms way of compiling things and the library only gets compiled into my generated javascript file when it is imported. So for this reason I should be able to have just a single elm-package.json file with all of the shared dependencies because the unused ones will not affect the file size of the resulting compile javascript files. So basically Hodor... and no fix needed. :)
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/madsflensted/elm-brunch/issues/19#issuecomment-217682070
Problem
I have a project with a structure similar to the following:
Each module has a different list of dependencies. How would you recommend using elm-brunch to build a project that can have multiple elm-package.json files?
Information