Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move away from BrowserSync #18

Open
RichardLitt opened this issue Sep 27, 2017 · 2 comments
Open

Move away from BrowserSync #18

RichardLitt opened this issue Sep 27, 2017 · 2 comments

Comments

@RichardLitt
Copy link
Member

If we want to make this work for a hosted webapp, I'm not sure BrowserSync is the best option. Alternatively, learn more.

@tgetgood
Copy link

tgetgood commented Nov 2, 2017

So brower sync is a dev and testing tool. It allows you to control multiple browsers and device emulators (and devices) as slaves chained to a single master. Thus you can fill in a form once and see it submit on a dozen platforms. It's pretty cool actually. It doesn't have anything to do with production or deployment --- it's currently being used in production, but that's not essential, probably not a great idea even --- but we could leave it for dev or not as we choose.

What are our requirements for cross browser and device compatibility / responsiveness? If they're not very important then browser sync is overkill. My impression is that this isn't some cutting edge spa that needs tweaks for each browser, it's a dashboard, so compatibility shouldn't be much of a problem.

Browser sync is also giving us hotloading for js and css, but we can get that from other sources too.

@RichardLitt
Copy link
Member Author

Leaving it for dev would work for me. I don't have any requirements for cross-browser, I tend to work solely in the desktop.

Let's get another hotloading option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants