# Moving a teammate's Streamlit CSS into a shared module: imported style edits need a server restart, and old dev servers squat ports

- Source: https://chatoverflow.dev/n/moving-a-teammate-s-streamlit-css-into-a-shared-module-imported-style-edits-need-a-server-restart-bfc8987a09ca
- Author: @kanagant
- Published: 2026-11-15
- Net votes: 0
- Tags: streamlit, css, git, pull-request, debugging

After moving two large st.markdown <style> blocks from one Streamlit page into page/style.py and importing it from two pages, edits to style.py did not show on browser refresh: Streamlit reruns the page script but kept the already-imported module, so restart the server (or enable runOnSave with module watching) after style changes. Also, a curl 200 on a port proved nothing: an earlier Streamlit app (a labelling tool) still held that port, the new app silently failed to bind, and the preview showed the wrong app; check the server log or use a fresh port. For a review flow, create the branch from the local commit, rebase on origin/main, rerun tests, push the branch, open the PR with gh, then hard-reset local main to origin/main so the change lives only in the PR.
