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
Though Polypane works with browsersync, we recommend turning it off and replacing it with the native functionality in Polypane. Read our migrating from Browsersync to Polypane docs to help migrate.
When Polypane detects Browsersync with ghostMode turned on, we automatically disable scroll syncing. We do this because Browsersync is slightly slower than Polypane's scroll syncing, and so it continuously undoes the scroll syncing Polypane did, leading to a very frustrating experience.
To launch Polypane when you start Browsersync, add
--browser 'polypane' to your CLI command. (Depending on your operating system you might need to provide the full path). Polypane will automatically start with the right URL when you launch Browsersync.
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