kylethebaker
Javascript Errors Stop Brunch Watcher, Full Restart Required
When running mix phx.server, anytime the watcher detects a javascript syntax error I get the standard js error message in the console, but any subsequent script changes don’t trigger a recompile. In order to get scripts to recompile I have to Ctrl-c and restart the server. It makes accidental syntax errors really frustrating. I have a feeling thing isn’t intended behavior.
This is also happening on a fresh 1.3 install using mix phx.new without any changes made, so I don’t think it is my application code.
Any idea what could be going on here?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 5 of 5 Posts!
NobbZ
I’m not sure what you are talking about. I’ve never experienced
phx.serverdoing anything related to brunch in any environment.Also I can’t find anything in phoenix or generated code which refers to using brunch on app start.
If doing JS-stuff I use a second terminal which has
brunch watchrunning. But I do prefer to just do not do anything JS related and if I had to touch a single file, I just do a single build, hoping I’m ready to go.kylethebaker
Maybe I should specify that this using the dev environment. In the default
config/dev.exsgenerated by phx.new there is a:watchersconfig field where you can specify external watchers. By default it includes brunch.After the watcher encounters an error in one of the watched scripts the watcher will stop detecting further changes, and the only way to restart the watcher in this case is to restart the server.
kylethebaker
I’ve figured out what was causing the watcher to crash. By default brunch will try to show errors with desktop notifications using notify-send. My dev environment is headless and doesn’t have notify-send installed which causes the watcher to crash on error. This can be avoided by adding
notifications: falsetobrunch-config.jskelvinst
Very cool you found this option!!! This was really a pain in the *ss for me, but I was not willing enough to ask the community or dig it a little more!! Thanks so much!
ericyoung
I develop exclusive within docker containers. Glad to find this fix of “notifications: false”, but it’s ridiculous that the watcher crashes just because my dev env can’t do the notify-send thing. A pull request to phoenix is needed to harden this up.