Better library example for Node

roblourens · roblourens · commit 8192b868104f · 2016-11-04T19:38:26.000-07:00
diff --git a/README.md b/README.md
@@ -52,8 +52,8 @@ The `sourceMapPathOverrides` option lets you set a mapping of source paths from
 If you set `sourceMapPathOverrides` in your launch config, that will override these defaults. `${workspaceRoot}` and `${cwd}` can be used here. If you aren't sure what the left side should be, you can use the `.scripts` command (details below). You can also use the `diagnosticLogging`/`verboseDiagnosticLogging` options to see the contents of the sourcemap, or look at the paths of the sources in Chrome DevTools, or open your `.js.map` file and check the values manually.
 
 ## Skipping "library code"/"blackboxed scripts"
-The `experimentalLibraryCode` option allows you to specify an array of names of folders/files to skip when debugging. For example, if you set `"experimentalLibraryCode": ["jquery.js"]`, then you will skip any file named 'jquery.js' when stepping through your code. You also won't break on exceptions thrown from 'jquery.js'. This works the same as "blackboxing scripts" in Chrome DevTools. Note that this is just an experiment at the moment. The format for entries is also the same, so you can add
-  * The name of a file (like `jquery.js`)
+The `experimentalLibraryCode` option allows you to specify an array of names of folders/files to skip when debugging. For example, if you set `"experimentalLibraryCode": ["lib.js"]`, then you will skip any file named 'lib.js' when stepping through your code. You also won't break on exceptions thrown from 'lib.js'. This works the same as "blackboxing scripts" in Chrome DevTools. Note that this is just an experiment at the moment. The format for entries is also the same, so you can add
+  * The name of a file (like `lib.js`)
   * The name of a folder, under which to skip all scripts (like `node_modules`)
   * A regex, to skip all scripts that match (like `\.min\.js$`)
 
