From 40023b5f4dd0106056aa9a65c25689a93312a882 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E7=8E=8B=E4=B8=8B=E9=82=80=E6=9C=88=E7=86=8A=28Chevalier?=
 =?UTF-8?q?=29?= <384924552@qq.com>
Date: Sun, 20 Aug 2017 22:29:51 +0800
Subject: [PATCH] Create WebDebug-Reference.md

---
 .../Web/EPractices/WebDebug-Reference.md            | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 Awesome-Reference/Web/EPractices/WebDebug-Reference.md

diff --git a/Awesome-Reference/Web/EPractices/WebDebug-Reference.md b/Awesome-Reference/Web/EPractices/WebDebug-Reference.md
new file mode 100644
index 0000000..e43cb9d
--- /dev/null
+++ b/Awesome-Reference/Web/EPractices/WebDebug-Reference.md
@@ -0,0 +1,13 @@
+# Web 开发调试学习与实践资料索引
+
+# JavaScript
+- [How to get the most out of the JavaScript console](https://parg.co/b9o): One of the most basic debugging tools in JavaScript is console.log(). The console comes with several other useful methods that can add to a developer’s debugging toolkit.
+- [debug【Project】](https://github.com/visionmedia/debug): tiny node.js & browser debugging utility for your libraries and applications.
+- [High-resolution JavaScript timer based on performance.mark/measure (461 bytes min+gz)](https://github.com/nolanlawson/marky)
+
+# VSCode
+
+# Chrome Dev Tools
+- [More helpful (and lesser known) features in the Chrome dev tools](https://blog.logrocket.com/making-the-most-of-the-chrome-developer-tools-8cac9a206979)
+- [Seeing backend performance in the Chrome dev tools](https://blog.logrocket.com/visualizing-backend-performance-in-the-chrome-devtools-bb6fd232540)
+- [Using the Chrome devtools new code coverage feature](https://parg.co/b4p)
-- 
GitLab