Polypane and local servers
Polypane works really well with automatic reloading tools like Browsersync or hot module reloading and can be easily started from code editors like Atom, Whisk and VS Code.
For more advanced integrations, check out Integrations
Using Polypane with Browsersync
Browsersync can sync the scroll position but because it's slightly slower than Polypane's scroll syncing, it continuously resets the scroll to a previous position, leading to a very frustrating experience.
Polypane will disable its scroll syncing when it detects Browsersync with "ghost mode" active to prevent this poor behavior. We recommend you turn off ghostMode in Browsersync and let Polypane handle all the event synchronisation.
Polypane will show a popup warning about this once per session for every page that it detects browsersync on.
Polypane accepts a url as an argument when starting, like other browsers. This enables you to set it as your browser in Browsersync. By adding
--browser 'polypane' (though depending on your operating system you might need to provide the full path), Browsersync will automatically start Polypane with the right URL. This also works with opn, webpack-dev-server and similar tools.
General SPA support
Polypane supports the history api so it works great out of the box with SPA routers that work without full page reloads.
Is your question not answered?
Ask via Twitter, Slack or our contact form