Open freyley opened 8 years ago
That sounds like a good idea to me.
Looks like we might be able to leverage Browsersync's notify method: https://www.browsersync.io/docs/api#api-notify
Improved error handling in general is definitely needed. We'll have to make sure errors like this don't interrupt the server.
We've been building components in Atom on one side of the screen, with the port-3000 Drizzle UI on the left side of the screen. When we had syntax errors, we had to switch to terminal to find the error that npm was spitting out - it'd have been awesome if the Drizzle UI had shown us that npm was erroring somehow.
Here are some examples of syntax errors that didn't kill npm, but did prevent us from seeing any change in Drizzle:
{{embed "patterns.components.pagination.base" }}{{/embed}}
(missing the#
on{{#
){{#embed "pattern.components.pagination.base"}}{{/embed}}
(missing thes
onpatterns
){{#embed patterns.components.pagination.base}}{{/embed}}
(missing the"
s on the location )