How we can enable live sass in devtools?
Base on Umaar post in own blog
https://umaar.com/dev-tips/103-live-sass/
To clarify "Enable CSS Source Maps" only allow your browser to show mappings between scss and css. Live SASS is is still experimental feauture. You'll be able to enable it by pressing SHIFT button six times on the experimental tab in the dev tools settings.
I tried it in latest unstable chrome build on Linux and it doesn't seem to work, so you'll need latest Canary build.
UPDATE:
It works in 53.0.2763.0 dev build on Linux.
Update:
Looking at this again, there appears to be a new experimental feature that is apparently in Chrome Canary, which takes out the need to run sass watch I think. However, I am unable to actually find where this gets enabled. I left my original answer as it may be of use still.
This is no longer an experimental feature. In Settings, make sure 'Enable CSS source maps' is enabled and (optionally) 'Auto-reload generated CSS'.
You can add your source files as a Workspace and live edit:
On a side note, to enable experimental features in Chrome, navigate to chrome://flags/, enable Developer Tools experiments and restart Chrome.
In Settings, you will see a new Experiments section:
Related
I want to use the LiveEdit plugin for debugging my website on PhpStorm. I have configured the plugin in the settings and even downloaded the JetBrains Chrome Extension and applied to Microsoft edge. I have also allowed the extension to read and write and make changes to all and every website. Yet, I don't see LiveEdit working.
I also have applied <all_urls> in extension settings - no progress. What should I do?
This should work for Edge in principle (as new Edge is Chromium-based), fixing WEB-45326 should take care of this.
For now, I'd suggest setting up Edge as a new custom browser in Settings | Tools | Web Browsers:
press + to add a new browser
use Chrome as a Family, specify a full path to browser executable as Path, enter a name
Browser will be available with Chrome icon in run configuration dropdown
even downloaded the JetBrains Chrome Extension and applied to Microsoft edge
Please remove it; Chrome extension doesn't work reliably in new Chrome versions (WEB-37230), and it seems that the most recent Chrome update has introduced breaking changes that made it non-functional. Since PhpStorm 2018.3 this extension is not required for debugging/Live Edit, it's not actively maintained, we plan to sunset it completely in the upcoming release
For the life of me I can't find where to enable this setting: Override requests with workspace project in Chrome Canary v64.0.3
Where do you enable this feature?
I learned about this feature from here: https://umaar.com/dev-tips/162-network-overrides/
Currently with 65 Chrome Canary it's not experimental anymore.
But you still cannot "Save for overrides" XHR requests.
This restriction is only in UI. To get XHR request override:
Open "Sources tab" in Chrome Canary DevTools and "Overrides" sub-tab under it.
Check "Enable Local Overrides" and add a folder to store changes in the filesystem.
Open "Network" tab in Chrome Canary DevTools and select XHR request
Press "Open in new tab"
Go to new opened tab Chrome DevTools - "Network"
Select the first request in the list and "Save for Overrides" button appears.
You can follow the gif from question starting step 5:
It's behind an experiment (https://developers.google.com/web/tools/chrome-devtools/ui#experiments) then it'll be under experiments in the settings panel of devtools.
Please do be warned though, this is an experimental feature, there are bugs and it might not work as intended.
We are trying hard to get it fully released soon (on Canary) but it needs to be a 1st class feature before we will feel ready to release it.
I think they might have shipped the feature, so it's no longer behind an experiment.
Try the workflow that Umaar outlined, omitting the step about enabling the experiment.
Haven't tried it myself yet, so I could be wrong
The feature is no longer an experiment in Chrome Canary (current version at the time of this: 64.0.3261.0). You can start to use it now. It will take a little time to arrive in Chrome stable.
In the latest version of Chrome Canary (Version 65.0.3317.2) you still need to enable dev tool experiments. The option is still behind the experiment flag #kayce-basques . I also followed the tutorial of Umaar - also using GitHub for testing - but I don't get any visible website changes after pressing F5.
Has someone figured out how to get it to work?
(1) Select the Overrides Tab in the Sources Panel.
(2) Click the Setup Overrides ( + icon) to add an empty folder.
(3) Confirm that Enable Network Overrides are enabled.
(4) Select the js file to be persisted on the Network Tab and display the source code in the code editor.
(5) Add code “console.log (‘hello world’);” to the beginning of the source code.
(6) Right click on the source code, select command [Save for overrides] on the context menu.
(7) Reload the current page after saving the file.
(8) Open the Console Panel and check the result.
This feature is now enabled in chrome stable you can follow these step:
In chrome go to "Sources tab" then in devtools "Overrides" click "Enable Local Overrides" then create a folder to put the changes in the filesystem. Go to
"Network" then select XHR request then "Open in new tab" then go to new opened tab Chrome DevTools - "Network"
pick the first request in the list and normally you will have a "Save for Overrides" button appears.
Sinсe Google Chrome was updated to 50.x version, it become impossible to work with DevTools. This issue reproduced mostly in "Network" tab. Every time when you click on "request" it takes about 30-40 sec. after that chrome can crash. Tried to delete all extensions, clear cache, and reinstall, but didn't help. Does anybody know how to fix this issue?
I'm running Chrome 50.0.2661.87 m
UPD: The problem may be occurs because of long headers. Try to close response and request headers.
I've been having similar issues for debugging in Chrome versions 50+ on Mac OS X 10.11.3. The only solution I've found so far is to keep the dev tools docked to the right and it seems to be as performant as before. Not the optimal solution, but it works in my case.
Finally, a solution has been found which helped me after such a long time and after so many failed attempts to fix it: Solution on Google Chrome Forums
Go to chrome://flags/#force-color-profile
Change it to sRGB
Since Google does not allow direct links to chrome:// you'll have to insert the colon by yourself, or enter the whole link manually into your toolbar.
My situation was similar, after struggling a while with extreme slow developer tools response I found out the problem was caused by a Chrome extension I had installed for knockoutJs.
So for people experiencing these issues, as part of the initial troubleshooting, try disabling chrome extensions.
I'm using the Version 61.0.3163.79 and I have the same issue that this post talks about.
With some searches I found out that the problem was in the user that I was using. What I tried was to enter int google chrome as guest and the devtools became faster again.
So what I did was:
Check out if debugging using the guest user is faster as it should be.
Logout from the account.
Clean all cache associated to google chrome.
Restart the PC (but i think closing the browser is enough)
Login again in your account.
I hope this could help other people with same problem.
[EDIT:]
I found out that after some time (weeks) the google chrome dev tools will get slower again. So I tried the following solution and it worked:
Open the dev tools
Go to the Sources tab.
Cleaned all watched variables, breakpoints, DOM breakpoint and Event Listeners breakpoint.
[SECOND EDIT:]
After some weeks, the issue came again. What I did was installing the google canary Version 64.0.3249.2 canary (64-bit) and my problems vanished.
For who's that doesn't know what is canary, please check this link.
Google is aware of the problem - https://bugs.chromium.org/p/chromium/issues/detail?id=624097
The problem seems to have vanished in v.53 - they are currently trying to figure out what fixed it. If possible, the fix will be merged back to v.52. But at least they are working on it.
In case others arrive here facing the same issue I had, try changing the Dev tools tab you're looking at to Elements.
I had the "Sources" tab open and Chrome was trying to load enormous assets for that tab, which created a multisecond delay between the console.log() events I created and the display of those logged messages.
Make devtools snappy again by deactivating all breakpoints:
Go to the Sources tab, show the debugger (may be hidden) and hit Deactivate breakpoints.
(Chrome v62.0 on Windows 10)
I've had the same time issue on 54.0.2840.99 m version of Google Chrome.
But switching to Chrome Canary worked !
Reduce size of resource being overridden
Only overriding files with less lines of code worked well for me. I landed here because I was overriding a file which had 35,000 + lines of Javascript.
Further, if your resource is a new one - i.e. it is not included in a script tag or link tag, you can override main html document and add the tag : <script src="/my-new-script.js"></script>. Add the file to your domain-root within the Overrides folder on Chrome:
overriding HTML
then overriding CUSTOM SCRIPT:
Good Luck...
I also face same issue.
I tried unchecked toggle screencast. Now it is working fine.
In my case, I had Local Overrides setup (https://developers.google.com/web/updates/2018/01/devtools#overrides) in Downloads folder which had a lot of files in it and that slowed down devtools.
Setting up overrides in its own seprate directory fixed the slowness.
I sped up Chrome again by doing the following:
Open DevTools -> select Elements tab ->
select nested Computed tab -> under Filter, make sure that Show all is unselected.
select nested Event Listeners tab -> make sure that Ancestors and Framework listeners are unselected.
For me, running Chrome Version 81.0.4044.138 (Official Build) (64-bit) on Ubuntu 18, the problem seems to be the mobile view. When I disable mobile view inspecting becomes really fast again. I think it is caused by touch emulation and other mobile stuff.
To have something similar to a mobile view I move the DevTools dock to the side and resize it until I get the width I need. It is not perfect, but it is useful most of the time.
Besides Chrome, Firefox is much faster when inspecting sites overall, though I didn't use FF because I'm used to specific things on Chrome. Moreover, most of the sites I work with do not trigger these issues on Chrome, in fact, it happens with only one site.
PD: the site that triggers the issue on Chrome Dev Tools has lots of CSS variables. Not sure if that is related.
UPDATE 1 WEEK ago
I was able to use Chrome without issues even in the mobile view by disabling the option "Show media queries"
Go to the network tool and change it without any restrictions. Sometimes this happens if you change mobile settings. Google chrome changes this setting to test mobile device on low internet connection and leaves it that way.
I used this nifty feature that chrome had for quite a while called "canvas inspector". It was an experimental dev feature that had to manually be enabled.
It was quite helpful when working with webgl via something like THREE.js where you can easily create a bunch of undesired draw calls by accident.
Also, it worked on any website, you could simply take a snapshot and see whats going on in the canvas.
It... miraculously disappeared one day, and google does not give any insight.
I've tried some extensions but they dont feel nearly as good, or i couldn't even get them to work. Is there another way to get this back into chrome?
Apparently it was doing some cheeky stuff that they didn't want in the main project so it was removed in this issue: DevTools: make Canvas profiler an extension
We can make it an extension though. This bug is for tracking removal of the canvas profiler from the DevTools. There will be a separate initiative of porting the code being removed into github and publishing it as a Chrome extension.
According to that issue they might move it to an extension in the future but I haven't found any traces of it as of now. They haven't responded to a question in the above issue about where the new issue could be tracked.
Chrome and Firefox have both removed their Canvas inspectors...
Original Answer:
This is not exactly what the question asks for, but Firefox has a canvas inspector integrated:
https://hacks.mozilla.org/2014/03/introducing-the-canvas-debugger-in-firefox-developer-tools/
You can enable it in the settings of the normal inspector
EDIT: (2019)
The Canvas Inspector has been removed as of Firefox 67:
Mozilla deprecated listing
Bug report with reasoning
Alternative:
spector.js - Recommended alternative by Mozilla
Canvas inspection was just removed!
You can download an old version of Chromium here like Chromium_OSX_43.0.2357.81.dmg. (Provided by freesmug)
Happy Canvas Inspection!
This is the best extension inspector I’ve seen so far.
https://spector.babylonjs.com
First go into
chrome://flags
Then enable
Developer Tools experiments
Then after restarting your browser, open the devlopers tools by hitting f12, then in the top right corner is a gear. Click on it, go to experiments, then find "canvas inspection". It's unstable, but usable.
I tried to enable support for sass source mapping in Chromium (v31.0.1606.0) but it seems that there is the "Support for SASS"-option missing in my case.
I followed those instructions:
http://fonicmonkey.net/2013/03/25/native-sass-scss-source-map-support-in-chrome-and-rails/
Screenshot of my "Experiments"-Window:
see http://i.stack.imgur.com/UhFNp.png
Hint: I also tried it with Google Chrome Canary and Chrome v30 and it didn´t worked either.
This one got me too, after reading a NetTuts article on Developing With Sass and Chrome DevTools. Seems like most articles on the subject are outdated.
Turns out Chrome v30 and later ship with souce maps and SASS support enabled by defualt. In v29 and earlier you have to check the "Support for SASS" box.
Furthermore, according to Google:
"Currently Sass is the only preprocessor that supports CSS source maps..."
So as long as you don't uncheck "Enable CSS Source Maps" in Dev Tools > Settings > General, you can hack away at your scss/sass directly from chrome.
I followed the Google Dev Tools docs and got it working on OSX.8 with Canary 32.0.1664.3. Here are the key points:
Make sure you're using sass 3.3.0alpha
gem install sass -v '>=3.3.0alpha' --pre
Add the --sourcemap flag when you run sass from shell
sass --watch --sourcemap sass/styles.scss:styles.css
Optionally enable "Auto-reload generated CSS" in Dev Tools > Settings > General for real-time goodness.
Here's a screenshot from my machine immediately after following the above steps and firing up a site with Sass.
Sources:
Working with CSS Preprocessors - Chrome DevTools – Google Developers
Developing With Sass and Chrome DevTools | Nettuts+