You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
In order to make this happen it's important to understand how the Chrome workspace feature works. This is my assumption:
User configures a workspace in Chrome
User visits website and Chrome looks at the URLs of the .css files
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
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)
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.
The text was updated successfully, but these errors were encountered: