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

Make SourceSync Compatible with Vite.js #2

Open
m5x5 opened this issue Jul 29, 2023 · 1 comment
Open

Make SourceSync Compatible with Vite.js #2

m5x5 opened this issue Jul 29, 2023 · 1 comment

Comments

@m5x5
Copy link
Owner

m5x5 commented Jul 29, 2023

From what I've seen Vite.js doesn't yet emit source maps in build mode. But we need a source file to correctly map the changes that Chrome does to the original file.

In addition to that we need the generated css file to be saved on the computer, otherwise Chrome won't be able to change the generated file.

@m5x5
Copy link
Owner Author

m5x5 commented Jul 31, 2023

In order to make this happen it's important to understand how the Chrome workspace feature works. This is my assumption:

  1. User configures a workspace in Chrome
  2. User visits website and Chrome looks at the URLs of the .css files
  3. If a CSS file for example is served from the route /styles/bundle.css it'll search for the same combination anywhere in the the folder you added as a workspace
  4. If a file was found in the workspace it'll be updated (maybe Chrome will check if the file content matches the file that was served)

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

1 participant