Alex Tan

@AndreaCrotti depends what the error is. If it's a syntax error in the migration file, [pgsanity](https://github.com/markdrago/pgsanity) can help find that. As for others, I would be interested in seeing more...

Seems like "File name does not match the module name" should replace "Misspelled the module name" as they're the same thing, right?

@AntonLebiodkin there's some explanation [here](https://package.elm-lang.org/packages/elm/http/latest/Http#expectStringResponse). You can replace Http.Error with your own custom error type and in the BadStatus case attempt to run a decoder on the body to get...

The approach [this](https://package.elm-lang.org/packages/austinshenk/elm-w3/4.0.0/) library takes solves at least some of the potential issues.

I would like to second @michaeljones scenario. This is a very common pattern we use in almost every Elm application/element in our company where there are several (in one case...

No, nothing called main in that file. I ended up resolving the issue by moving the file to a nested directory, though didn't figure out what was causing the issue.

I'm seeing this issue as well. Adding this to my package.json fixed this for me.

@AleXoundOS I started working to make it compatible with elm/http 2.0 and elm 0.19 on [this branch](https://github.com/alex-tan/elm-postgrest/tree/http-2) a while back. If I recall correctly it should be in a mostly...

@deivid-rodriguez I checked that the versions match on both machines. If it was using a different version and changing the lockfile wouldn't it update the `BUNDLED WITH` section? I'm asking...

Yeah I confirmed there's no bundler version mismatch warning for those that are having issues.