Browser-sync conflicting with express-session

[pietrodesiato]

I am having issues when using BrowserSync together with Express-session. This seems to be related to the page refresh that BrowserSync triggers, which apparently clears some of the session variables.

In general, should BrowserSync be installed by default?

[rpowis]

@pietrodesiato It depends on what you're trying to do and and what's causing the refresh...

If you're changing CSS then you shouldn't be seeing a page refresh as the updated CSS just gets injected straight into the page. That won't create a new session.

If you're changing HTML or JS though then that will cause a page refresh and therefore create a new session.

I think it should be enabled by default as it improves the dev process, but maybe we could add an HTML injector as a plugin? either that or persist data without sessions.

[pietrodesiato]

I am changing session variables that then affect the 'checked' value of a checkbox.

I'd like to hear what the other designers think.
For me it's quite annoying and I'd rather have if off by default. Then developers can enable it if they need.

I didn't know what BrowserSync was and when I saw all my browsers updating at the same time I thought my computer went crazy. I figure it out only after.