Unless someone says otherwise that does sound like a bug and should be reported. I've always thought it was case sensitive as I use linux and even on Windows it yells at me with such a warning if not a precise match (although that might be cygwin'isms).
On Saturday, October 1, 2016 at 1:07:19 PM UTC-6, Wil C wrote: > > UGH. I figured out what it was. Elm modules with multiple words are > camelcased, and so should the filenames. > > On localhost (mac), it's not case sensitive. code_fragment compiles module > CodeFragment. But on production (ubuntu) it is. > > Should I submit an issue ticket on getting a warning or error when > compiling when the name of module doesn't match with filename? > > Wil > > On Thursday, September 29, 2016 at 2:40:04 PM UTC-7, OvermindDL1 wrote: >> >> Not really, exrm is pretty easy (I've not migrated to distillery yet, I >> have an old project), but I did find >> https://github.com/epsanchezma/exrm-heroku although it appears pretty >> old but could try it, if it works then exrm could deploy straight to heroku. >> >> >> On Thursday, September 29, 2016 at 2:06:49 PM UTC-6, Wil C wrote: >>> >>> I checked on both, and they're both elm 0.17.1 >>> >>> [ruby-2.2.0 ~/projects/code/pithy master] >>>> > elm -v >>>> 0.17.1 >>>> [ruby-2.2.0 ~/projects/code/pithy master] >>>> > heroku run "elm -v" >>>> Running elm -v on ⬢ pithy... up, run.5500 >>>> 0.17.1 >>> >>> >>> Yeah, I'm using Phoenix. Ah, I just wanted something simple to get up >>> and running, so I didn't mess around with exrm or distillery. When I have >>> more time, I'll get that going instead. Got any tips or links to a write up >>> on how to package it up in exrm/distillery and throw it on heroku? >>> >>> >>> Wil >>> >>> >>> >>> On Thursday, September 29, 2016 at 7:19:31 AM UTC-7, OvermindDL1 wrote: >>>> >>>> Hmm, I use the same type of setup with the same type of arguments as >>>> you though I've not tried heroku. Is the elm version between your dev >>>> machine and heroku the same? It looks like you might be using phoenix, >>>> you >>>> really should be generating a production output of all files on your dev >>>> server so that manifests are built, code is optimized, and everything is >>>> packed together into a release (via exrm or distillery) and you should >>>> deploy that release to heroku instead as it is entirely self-contained and >>>> standalone. I use the release process and never had an issue. >>>> >>>> >>>> On Thursday, September 29, 2016 at 3:06:55 AM UTC-6, Wil C wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I have a puzzling situation that I hope someone can shed some light >>>>> on. I'm using elm with elixir, and compiling it with elm-brunch. I'm able >>>>> to 'brunch build' without a problem locally, but on the remote heroku >>>>> servers, I get the following problem: >>>>> >>>>> remote: Running default compile >>>>>> remote: Elm compile: src/rei.elm, in web/elm, to >>>>>> ../static/vendor/rei.js >>>>>> remote: *I cannot find module 'Codefragment'.* >>>>>> remote: >>>>>> remote: Module 'Rei' is trying to import it. >>>>>> remote: >>>>>> remote: Potential problems could be: >>>>>> remote: * Misspelled the module name >>>>>> remote: * Need to add a source directory or new dependency >>>>>> to elm-package.json >>>>>> remote: 29 Sep 08:42:47 - error: Compiling of >>>>>> web/elm/src/rei.elm failed. Command failed: >>>>>> ../../node_modules/elm/binwrappers/elm-make --yes --output >>>>>> ../static/vendor/rei.js src/rei.elm >>>>>> remote: I cannot find module 'Codefragment'. >>>>>> remote: >>>>>> remote: Module 'Rei' is trying to import it. >>>>>> remote: >>>>>> remote: Potential problems could be: >>>>>> remote: * Misspelled the module name >>>>>> remote: * Need to add a source directory or new dependency >>>>>> to elm-package.json >>>>>> remote: >>>>> >>>>> >>>>> I checked that the source_directories are set. my elm-package.json is: >>>>> >>>>> >>>>> { >>>>>> "version": "1.0.0", >>>>>> "summary": "helpful summary of your project, less than 80 >>>>>> characters", >>>>>> "repository": "https://github.com/user/project.git";, >>>>>> "license": "BSD3", >>>>>> >>>>>> >>>>>> *"source-directories": [ "src" ],* >>>>>> "exposed-modules": [], >>>>>> "dependencies": { >>>>>> "elm-lang/core": "4.0.5 <= v < 5.0.0", >>>>>> "elm-lang/html": "1.1.0 <= v < 2.0.0" >>>>>> }, >>>>>> "elm-version": "0.17.1 <= v < 0.18.0" >>>>>> } >>>>> >>>>> >>>>> All the elm files are under web/elm/src. my brunch's config files for >>>>> elm is: >>>>> >>>>> plugins: { >>>>>> elmBrunch: { >>>>>> elmFolder: "web/elm", >>>>>> >>>>>> >>>>>> *mainModules: [ "src/rei.elm" ],* >>>>>> outputFolder: "../static/vendor", >>>>>> executablePath: "../../node_modules/elm/binwrappers" >>>>>> }, >>>>>> babel: { >>>>>> // Do not use ES6 compiler in vendor code >>>>>> ignore: [/web\/static\/vendor/] >>>>>> } >>>>>> }, >>>>> >>>>> >>>>> Reading brunch-elm code >>>>> <https://github.com/madsflensted/elm-brunch/blob/master/index.js>and >>>>> the mainModules should be correct. However, through trial and error, >>>>> "src/rei.elm" fails on production, but not on my local machine. However, >>>>> using "src/*.elm" seems to not fail in production, but while it compiles, >>>>> it doesn't seem to write to the output. >>>>> >>>>> Has anyone else run into this? It seems like elm-make has a different >>>>> behavior on macos, compared to on heroku. >>>>> >>>>> For now, I'm just committing the generated file to the repo, which >>>>> works. But I'd rather have the file build in production. If someone has >>>>> something to shed the light on this, I'd really appreciate it. >>>>> >>>>> Wil >>>>> >>>> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
