Special statement

This article is a series by Tomek Sułkowski published on Medium. The copyright belongs to the original author. The translator had already communicated with the author before the translation to get permission to translate the whole series. In order not to disturb your reading, the record of authorization is here

The body of the

In the 24 days leading up to the holiday season, I will be publishing a series of short articles on how to use development tools in a more interesting way. Yesterday we mentioned four, so today we will start with this number…

5. copy(…)

You can use the global copy() method to copy any resources you can on console, including the variables we mentioned in the previous article. For example copy($_) or copy($0)

6. Store as global

If you print a bunch of data in console (such as an array computed in your App) and you want to do something extra with that data, for example, using copy we just said, you can easily convert it to a global variable:

Just right click and select the “Store as Global variable” option.

The first time you use it, it creates a variable called temp1, temp2 and so on. So you can manipulate all kinds of data without worrying about it being copied.

Save the Stack trace

Stack trace information will be useful to you and your colleagues. (e.g., working with other front-end developers or QA engineers). So we can just save the stack trace as a file instead of a screenshot.

8. Copy HTML (fastest way)

Maybe you know that right click or click on the ellipsis (…) next to the HTML element. You can copy it to the operating system clipboard but you can do the same with the very old [CTRL] + [c] + [CTRL] + [v] method!

That’s it for today, a short but heartwarming routine: If you learn something new

→ Follow me on Twitter Tomek Sułkowski

Other series

Other articles in this series will be translated soon, with links posted here.

  • Day 1: ‘$’ in the Console
  • Tips you might not know about Chrome debugging tools Day 2: Copying & Saving
  • Chrome debugging tools you didn’t know about
  • The Chrome debugging tool has a few tricks you don’t know about.
  • Day 5: Console log, puzzling case
  • You don’t know the Command menu for Chrome
  • 7. Fun tips you didn’t know about the Chrome Debugging Tool Consle
  • Chrome’s Color picker is a Color picker that you don’t know about.
  • Day 9: Time console
  • Custom Formatters are custom formatters for Chrome.
  • Today: Style Editors continued
  • Tips you don’t know about the Chrome Debug Tool Day 12: Ninja Log Print! (the ninja logs)
  • Chrome debugging Tool tips you didn’t know about
  • Chrome Debugging Tool tips you didn’t know About day 14: Other shortcuts
  • Chrome debugger tips you didn’t know about
  • Tips you don’t know about Chrome debugging Tools 16: Breakpoints
  • Day 17: Farewell to Console
  • What you Didn’t know about Chrome Debug Tools
  • Chrome debug tool tips you don’t know
  • Tips you didn’t know about Chrome debugging tools Day 20: The dark arts of Workspace
  • Tips you Don’t Know about Chrome Debugging Tools Day 21: Snippets
  • Chrome Debugging Tool tips you didn’t know
  • Chrome debug Tool tips you don’t know
  • Day 24: The last day, New Year’s Day, is awesome

Write in the last

If you are sure of my translation, you can also pay attention to my wave oh ~ incidentally my open source project, for a wave of star→ see here, beautiful blog system