Christian Heilmann

Syncing CSS changes in browser developer tools with Workspaces

Tuesday, March 2nd, 2021 at 11:25 am

Lately I’ve been looking into improving the ways I use browser developer tools by using features I’ve never looked and/or forgotten. One amazing feature of those are Workspaces which have been around for a long time but don’t get as much use as I think they should.

Workspaces: use visual developer tools to change live code in your project

In essence, this feature allows you to use the visual tools in the developer tools to tweak and change styles in a more persistent manner. Instead of having to copy and paste the changes you made back into your CSS files in your editor, using Workspaces allows Browser Developer Tools to directly change files on the hard drive. That way you sync changes with your editor.

You can see this in action in this video on YouTube.

In the video, I cover the following steps:

  • Dragging a project folder into Visual Studio Code to have all files to edit
  • Opening the integrated terminal in VS Code to start a local server using “php -s localhost:8000”.
  • Changing the project styles using the Colour picker and the Font editor
  • Copy whole changed CSS files using the Sources panel
  • Using the Command Menu to access functionality of the tools
  • Using the Changes panel to track individual changes in your CSS files caused by using the developer tools
  • Dragging the project folder into the Sources panel of developer tools
  • Allowing the developer tools to access the hard drive to sync changes
  • Using the developer tools to change CSS files directly in sync with Visual Studio Code.

Share on Mastodon (needs instance)

Share on BlueSky

Newsletter

Check out the Dev Digest Newsletter I write every week for WeAreDevelopers. Latest issues:

Don't stop thinking, AI Slop vs. OSS Security, rolling your own S3 Despite AI you still need to think, Bitter lessons from building AI products,  AI Slop vs. OSS security and pointer pointer…
200: Building for the web, what's left after rm -rf & 🌊🐴 vs AI What remains after you do a rm -rf? Why do LLMs know about a seahorse emoji? What image formats should you use? How private is your car?
Word is Doomed, Flawed LLM benchmarks, hard sorting and CSS mistakes Spot LLM benchmark flaws, learn why sorting is hard, how to run Doom in Word and how to say "no" like a manager.
30 years of JS, Browser AI, how attackers use GenAI, whistling code Learn how to use AI in your browser and not on the cloud, why AI makes different mistakes than humans and go and whistle up some code!
197: Dunning-Kruger steroids, state of cloud security, puppies>beer

My other work: