Use `repl` command ( see third example in [docs][1] ) 


    break in hotplate/node_modules/bd/lib/bd.js:133
    132 
    133   debugger;
    134 
    135   // Delete the ID and the version since there&#39;s no point,
    debug&gt; repl
    Press Ctrl + C to leave debug repl
    &gt; Workspace


  [1]: http://nodejs.org/api/debugger.html

Update: bonus question - https://github.com/c4milo/node-webkit-agent


The answer to the bonus question has changed in 2018.

Run `node inspect foo.js`.

Visit `chrome://inspect` and in the list of devices you should see an entry that says `Target (&lt;process.version&gt;)` with an accompanying inspect link.

It looks like this:
[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/B9nQb.png

I can get WiFi signal level in dBm using following code.

    for (ScanResult result : wifiScanResultList) {
    	int signalLevel = result.level;
    }

It gives negative value. When we see the default system WiFi setting and clicked on the connected WiFi network, it gives &quot;Good&quot; or &quot;Bad&quot; as signal strength. What is the range that we can filter those negative vales as &quot;Good&quot; signal strength or &quot;Bad&quot; signal strength?

Getting WiFi signal strength in Android

I have the `item` object and i need to pass that along many pages to store data in single item

LIke my item is

    class DmozItem(Item):
        title = Field()
        description1 = Field()
        description2 = Field()
        description3 = Field()



Now those three description are in three separate pages. i want to do somrething like

Now this works good for `parseDescription1`

 

    def page_parser(self, response):
        sites = hxs.select(&#39;//div[@class=&quot;row&quot;]&#39;)
        items = []
        request =  Request(&quot;http://www.example.com/lin1.cpp&quot;,  callback =self.parseDescription1)
        request.meta[&#39;item&#39;] = item
        return request 
            
    def parseDescription1(self,response):
        item = response.meta[&#39;item&#39;]
        item[&#39;desc1&#39;] = &quot;test&quot;
        return item

But i want something like

    def page_parser(self, response):
        sites = hxs.select(&#39;//div[@class=&quot;row&quot;]&#39;)
        items = []
        request =  Request(&quot;http://www.example.com/lin1.cpp&quot;,  callback =self.parseDescription1)
        request.meta[&#39;item&#39;] = item

        request =  Request(&quot;http://www.example.com/lin1.cpp&quot;,  callback =self.parseDescription2)
        request.meta[&#39;item&#39;] = item

        request =  Request(&quot;http://www.example.com/lin1.cpp&quot;,  callback =self.parseDescription2)
        request.meta[&#39;item&#39;] = item

        return request 
            
    def parseDescription1(self,response):
        item = response.meta[&#39;item&#39;]
        item[&#39;desc1&#39;] = &quot;test&quot;
        return item

    def parseDescription2(self,response):
        item = response.meta[&#39;item&#39;]
        item[&#39;desc2&#39;] = &quot;test2&quot;
        return item

    def parseDescription3(self,response):
        item = response.meta[&#39;item&#39;]
        item[&#39;desc3&#39;] = &quot;test3&quot;
        return item

How can i use multiple requests and pass items in between them in scrapy python

I am trying to use the node debugger.
I am running `node debug server` to run my server. Then I have:

    ...
    var Workspace = mongoose.model(&#39;Workspace&#39;);
    debugger;

At this point, as expected, when I run this code the debugger pops up.
However, I would expect it to have all of the current variables set, like it happens in Chrome&#39;s own debugger.

But:

    break in hotplate/node_modules/bd/lib/bd.js:133
    132 
    133   debugger;
    134 
    135   // Delete the ID and the version since there&#39;s no point,
    debug&gt; Workspace
    ReferenceError: Workspace is not defined

So... how do I _actually_ inspect the current variables?

Bonus question: is there ANY way to use Chrome&#39;s developers tools (CTRL-J) so that it connects to the node and works that way? (I am aware of node-inspector, but it&#39;s very outdated and...)

Inspecting variables using node&#39;s built-in debugger?

I am trying to use the node debugger.
I am running <code>node debug server</code> to run my server. Then I have:
<pre><code class="hljs language-ini">...
var Workspace = mongoose.model('Workspace');
debugger;
</code></pre>
At this point, as expected, when I run this code the debugger pops up.
However, I would expect it to have all of the current variables set, like it happens in Chrome's own debugger.
But:
<pre><code class="hljs language-javascript">break in hotplate/node_modules/bd/lib/bd.js:133
132 
133 debugger;
134 
135 // Delete the ID and the version since there's no point,
debug> Workspace
ReferenceError: Workspace is not defined
</code></pre>
So... how do I actually inspect the current variables?
Bonus question: is there ANY way to use Chrome's developers tools (CTRL-J) so that it connects to the node and works that way? (I am aware of node-inspector, but it's very outdated and...)

I can&#39;t find a way how to stop some part of `it`&#39;s from run if one of them failed

I&#39;m using `mocha-as-promised`, so the code might look different from as usuall


&lt;!-- language: lang-js --&gt;

    describe(&quot;remote promises&quot;, function() {
      describe(&quot;browsing&quot;, function() {
        describe(&quot;getting page&quot;, function() {
          it(&quot;should navigate to test page and check title&quot;, function() {
            this.timeout(TIMEOUT);
            return browser.get(&quot;http://admc.io/wd/test-pages/guinea-pig.html&quot;).then(function() {
              return browser.title();
            }).then(function(title) {
              return assert.ok(~title.indexOf(&quot;I am a page title - Sauce Labs&quot;), &quot;Wrong title!&quot;);
            });
          })
          it(&quot;submit element should be clicked1&quot;, function() {
            this.timeout(TIMEOUT);
            return browser.elementById(&quot;submit&quot;).then(function(el) {
              return browser.clickElement(el);
            }).then(function() {
                return browser[&quot;eval&quot;](&quot;window.location.href&quot;);
              }).then(function(location) {
                assert.ok(~location.indexOf(&quot;http://&quot;), &quot;Wrong location!&quot;);
              });
          })
        });
        describe(&quot;clicking submit&quot;, function() {
          it(&quot;submit element should be clicked2&quot;, function() {
            this.timeout(TIMEOUT);
            return browser.elementById(&quot;submit&quot;).then(function(el) {
              return browser.clickElement(el);
            }).then(function() {
                return browser[&quot;eval&quot;](&quot;window.location.href&quot;);
              }).then(function(location) {
                assert.ok(~location.indexOf(&quot;http://&quot;), &quot;Wrong location!&quot;);
              });
          });
        });
  
      });
    });

and i want that if `should navigate to test page and check title` is failed then 
`submit element should be clicked1` should be skipped


EDIT:
seems i&#39;m just making my tests wrong, will wait for some time before deleting question

**EDIT:**

as i replied in comment - i already received this answer in mocha google groups, but there are some other restrictions i not mentioned in question - i&#39;m using grunt-simple-mocha and as i inspected code - there is no bail option when i pass options to mocha constructor

i failed to find where are options from command line are passed to Suite instance, and the only line where it may be as i see it is a

    suite.bail(this.bail());

which looks weird for me

i think i will open issue at mocha github pages, maybe they will extend passed options with bail setting later, or just explain me what i did wrong and how i can solve my problem in other way

**EDIT: and now, according to https://github.com/visionmedia/mocha/commit/f0b441ceef4998e570a794dcff951bf2330eb0c5
latest Mocha have bail option from the box. Thanks to authors!**

Skip subsequent Mocha tests from spec if one fails

In a node.js script that I&#39;m working on, I want to print all node.js modules (installed using npm) to the command line. How can I do this?

    console.log(__filename);
    
    //now I want to print all installed modules to the command line. How can I do this?

Print a list of all installed node.js modules

I&#39;m about to attempt my first AngularJS project, and it makes sense to use Node.js for the back end, even though it means learning both AngularJS and Node.js from scratch at the same time.

The first thing I&#39;m trying to get my head around is a good file structure. So far my pure HTML/CSS template has the following directory structure...

    _site/
    Fonts/
    Javascript/
    SASS/
    Stylesheets/
    Index.html

( _site is a working directory for PSDs, etc.)

I found an example directory structure for a Node.js/AngularJS app [here][1]....

... which suggests the following directory structure.

    app.js              --&gt; Application configuration
    package.json        --&gt; For npm
    public/             --&gt; All of the files to be used in on the client side
      css/              --&gt; CSS files
        app.css         --&gt; Default stylesheet
      img/              --&gt; Image files
      js/               --&gt; JavaScript files
        app.js          --&gt; Declare top-level application module
        controllers.js  --&gt; Application controllers
        directives.js   --&gt; Custom AngularJS directives
        filters.js      --&gt; Custom AngularJS  filters
        services.js     --&gt; Custom AngularJS services
        lib/            --&gt; AngularJS  and third-party JavaScript libraries
          angular/
            angular.js            --&gt; The latest AngularJS
            angular.min.js        --&gt; The latest minified AngularJS
            angular-*.js          --&gt; AngularJS add-on modules
            version.txt           --&gt; Version number
    routes/
      api.js            --&gt; Route for serving JSON
      index.js          --&gt; Route for serving HTML pages and partials
    views/
      index.jade        --&gt; Main page for the application
      layout.jade       --&gt; Doctype, title, head boilerplate
      partials/         --&gt; AngularJS view partials (partial jade templates)
        partial1.jade
        partial2.jade

So, this looks quite good to me (except for the fact that I wouldn&#39;t use Jade).

I still have the following questions...

1. I want to keep all front-end and back-end files separate. This solution puts all the front-end files in the public/ directory which kind of makes sense because most need to be public, but does it make sense to put the SASS and _site folders here? I could just keep them there, but not upload them when I put them into production, but it seems wrong because they shouldn&#39;t be public. They also don&#39;t belong at root level with all the back-end stuff.

2. Wouldn&#39;t it be better to load AngularJS from a [CDN][2]?

3. Given that the server will only need to deliver one template (the main application template) and all other HTML will be constructed on the front-end wouldn&#39;t it make more sense to keep the index.html file static, delete the views folder and create a partials/ folder under public/ like the original AngularJS Seed application does?

I realize that this is all a matter of opinion, and I could technically put them wherever I want, but I&#39;m hoping somebody more experienced than me could advise me of the pitfalls of various directory structures.

  [1]: https://github.com/btford/angular-express-seed
  [2]: http://en.wikipedia.org/wiki/Content_delivery_network



Structuring a Node.js and AngularJS application

I&#39;m using Passport.js for authentication (local strategy) and testing with Mocha and Supertest.

How can I create a session and make authenticated requests with Supertest?

How to authenticate Supertest requests with Passport?

I am currently using the following for hashing passwords:

    var pass_shasum = crypto.createHash(&#39;sha256&#39;).update(req.body.password).digest(&#39;hex&#39;);

Could you please suggest improvements to make the project safer?



Node.js hashing of passwords

I just encountered a DEBUG macro in C that I really like


    #ifdef DEBUG_BUILD
    #  define DEBUG(x) fprintf(stderr, x)
    #else
    #  define DEBUG(x) do {} while (0)
    #endif

I&#39;m guessing a C++ analogue would be :-

    #ifdef DEBUG_BUILD
    #  define DEBUG(x) cerr &lt;&lt; x
    #else
    #  define DEBUG(x) do {} while (0)
    #endif

 1. Is the second code snippet analogous to the one in C?
 2. Do you have any favorite C++ debug macros?

EDIT : 
By &quot;Debug Macros&quot; I mean &quot;macros that might come in handy while running a program in debug mode&quot;.

DEBUG macros in C++

I have a problem connecting HTC Wildfire A3333 in debugging mode with my Fedora Linux 17. Adb says:

    ./adb devices
    List of devices attached 
    ????????????	no permissions

my udev rules (first rule for Samsung which works just fine and second for HTC which is not):

    SUBSYSTEM==&quot;usb&quot;,SYSFS{idVendor}==&quot;04e8&quot;,SYMLINK+=&quot;android_adb&quot;,MODE=&quot;0666&quot;,GROUP=&quot;plugdev&quot; 
    SUBSYSTEM==&quot;usb&quot;,SYSFS{idVendor}==&quot;0bb4&quot;,SYMLINK+=&quot;android_adb&quot;,MODE=&quot;0666&quot;,GROUP=&quot;plugdev&quot;


For Samsung devices everything&#39;s okay:

     ./adb devices
    List of devices attached 
    00198a9422618e	device


I have been trying all of the answers given in a simmilar thread wthout any luck: https://stackoverflow.com/questions/3947729/using-htc-wildfire-for-android-development

Android Debug Bridge (adb) device - no permissions

I have to debug a program that has errors in it as part of my assignment. However, I must first pass command line arguments in order to solve this problem.

I do:

    gdb -tui InsertionSortWithErrors

which works, but after that I don&#39;t know how to pass arguments. I used `gdb -help` and it says something about `--args` which I also tried and it didn&#39;t work.

I want to be able to get the debugger+the GUIand pass command line arguments.



How do I pass a command line argument while starting up GDB in Linux?

When using [Safari Web Inspector][1] to read the JavaScript console output, the log is reset upon navigation i.e. going from page *index.html* to *mail.html* clears the console output. In the [Chrome Developer Tools][2], I can easily preserve the log by right clicking on the console space and selecting *Preserve Log Upon Navigation*. With this option, console log output remains intact until I manually clear the output simplifying the process of debugging JavaScript that refreshes or redirects to another page. 

Is there a similar feature in Safari Web Inspector? 


  [1]: https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html
  [2]: https://developers.google.com/chrome-developer-tools/docs/console

Safari Developer Tools: How to Preserve Console Log Upon Navigation?

`list` commands prints a set of lines, but I need one single line, where I am and where an error has probably occurred.



Content Type	Original Author	Original Content on Stackoverflow
Question	Merc	View Question on Stackoverflow
Solution 1 - node.js	Andrey Sidorov	View Answer on Stackoverflow
Solution 2 - node.js	Andy Gaskell	View Answer on Stackoverflow

Inspecting variables using node's built-in debugger?

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Solution 2 - node.js

How can i use multiple requests and pass items in between them in scrapy python

Getting WiFi signal strength in Android

Attributions