To set a global variable, use `global` instead of `window`.

    global[&quot;myvar&quot;] = value

I am dynamically adding columns to a table by using `document.createElement(&quot;th&quot;)`

    var newTH = document.createElement(&#39;th&#39;);

Is there a way to set an `onClick` attribute for this so a user can delete the column by clicking on the header? Any help would be great. If this is not possible, is it possible to put something in 

    newTH.innerHTML

to make it work? 

Add onClick event to document.createElement(&quot;th&quot;)

I have this HTML structure:

    &lt;div id=&quot;body&quot;&gt;
        &lt;div id=&quot;head&quot;&gt;
            &lt;p&gt;Dynamic height without scrollbar&lt;/p&gt;
        &lt;/div&gt;
        &lt;div id=&quot;content&quot;&gt;
            &lt;p&gt;Dynamic height with scrollbar&lt;/p&gt;
        &lt;/div&gt;
        &lt;div id=&quot;foot&quot;&gt;
            &lt;p&gt;Fixed height without scrollbar&lt;/p&gt;
        &lt;/div&gt;  
    &lt;/div&gt;



I want to have the three parts inside the main part (#body) without overflow. So I need a scroll bar in the middle part.


I tried this CSS:

    #content{
        border: red solid 1px;
        overflow-y: auto;
    }

And this:


    #content{
        border: red solid 1px;
        overflow-y: auto;
        height: 100%;
    }

But neither of them work.

I made an example at [JSFiddle](http://jsfiddle.net/6WAnd/).

Can I do this with only CSS and HTML? I&#39;d prefer to avoid Javascript.

Scrollbar without fixed height/Dynamic height with scrollbar

What is the node.js equivalent of `window[&quot;myvar&quot;] = value`?

What is the node.js equivalent of window[&quot;myvar&quot;] = value?

<p>What is the node.js equivalent of <code>window["myvar"] = value</code>?</p>


I have the following code:

    alert($embellishment.data(&quot;embellishmentId&quot;));
    alert($embellishment.attr(&quot;data-embellishmentId&quot;));

The first alert returns `undefined`, whereas the second alert returns an integer, `3`.

[**-- SEE DEMO --**][1]

I&#39;m using jQuery version 1.7.2 (`data` was added with version 1.4 I believe)

Why is this? Should I be using `data()` at all if its not returning the right values?


  [1]: http://jsfiddle.net/6Pdj6/

jQuery data() returns undefined, attr() returns integer

Is there a way in Javascript to write something like this easily:

    [1,2,3].times do {
      something();
    }

Any library that might support some similar syntax maybe?

**Update:** to clarify - I would like `something()` to be called 1,2 and 3 times respectively for each array element iteration

do &lt;something&gt; N times (declarative syntax)

This question is just to clear some things up. Some things like this have been asked before, and this rounds them all up into one question - where should JavaScript go in the HTML document, or, more importantly, does it matter? So, one of the things I&#39;m asking is, does

    &lt;head&gt;
    &lt;script type=&quot;text/javascript&quot;&gt;
    alert(&quot;Hello world!&quot;);
    &lt;/script&gt;
    &lt;/head&gt;

at all differ (in terms of functionality) from

    &lt;body&gt;
    &lt;!-- Code goes here --&gt;
    &lt;script type=&quot;text/javascript&quot;&gt;
    alert(&quot;Hello world!&quot;);
    &lt;/script&gt;
    &lt;/body&gt;

More importantly, I want to focus on JS that modifies or uses elements from the DOM in any way. So I know that if you put something like `document.getElementById(&quot;test&quot;).innerHTML = &quot;Hello world!&quot;` before `&lt;element id=&quot;test&quot;&gt;&lt;/element&gt;` in your body, then it won&#39;t work since the body is loaded from top to bottom, making the JS load first, which will then proceed to try to manipulate an element that doesn&#39;t exist yet. So it should, just like the above, either go in the `&lt;head&gt;` or just before the `&lt;/body&gt;` tag. The question is, aside from organisation and sorting, does it matter which one of these is chosen, and if so, in what way?

Of course, there is also a third method - the jQuery way:

    $(document).ready(function(){ /*Code goes here*/ });

That way, it doesn&#39;t matter where in the body you place the code, since it will only be executed when everything has loaded. The question here is, is it worth importing a huge JS library *just* to use a method the need for which could be replaced with an accurate placing of your scripts? I&#39;d just like to clear things up a little here, if you would like to answer, go ahead! Summary: where should different kinds of scripts go - head or body, and/or does it matter? Is jQuery worth it just for the ready event?

JavaScript - head, body or jQuery?

I&#39;m creating an API that returns results as JSON. Is there a current best practice for whether we should include keys in the result when the value is null?  For example:

&lt;!-- language: lang-js --&gt;

    {
        &quot;title&quot;:&quot;Foo Bar&quot;,
        &quot;author&quot;:&quot;Joe Blow&quot;,
        &quot;isbn&quot;:null
    }

or

&lt;!-- language: lang-js --&gt;

    {
        &quot;title&quot;:&quot;Foo Bar&quot;,
        &quot;author&quot;:&quot;Joe Blow&quot;
    }

Since the second is smaller I am leaning towards this style, but I&#39;m not sure if there is a preferred style or not. From a client perspective it seems like both styles would be functionally equivalent. Any pros or cons to each?


Should JSON include null values

I am trying to use the *ng-click* feature of AngularJS to switch views. How would I go about doing this with the code below?

index.html
   

     &lt;div ng-controller=&quot;Cntrl&quot;&gt;
            &lt;div ng-click=&quot;someFunction()&quot;&gt;
                click me
            &lt;div&gt;
        &lt;div&gt;
    
controller.js
  

      function Cntrl ($scope) {
            $scope.someFunction = function(){
                //code to change view?
            }
        }



AngularJS : How do I switch views from a controller function?

For example I want to use custom logger:

    logger = require(&#39;basic-logger&#39;),
    logger.setLevel(&#39;info&#39;)

    var customConfig = {
    showMillis: true,
    showTimestamp: true
    }

    var log = new logger(customConfig)

How to use this logger in other modules instead of console.log ?

How to use global variable in node.js?

I&#39;ve written a REST API on the express framework for node.js that works for requests from the js console in Chrome, and URL bar, etc. I&#39;m now trying to get it working for requests from another app, on a different domain (CORS).
 
The first request, made automatically by the javascript front end, is to /api/search?uri=&lt;value&gt;, and appears to be failing on the &quot;preflight&quot; OPTIONS request. 

In my express app, I am adding CORS headers, using:

    var allowCrossDomain = function(req, res, next) {
        res.header(&#39;Access-Control-Allow-Origin&#39;, &#39;*&#39;);
        res.header(&#39;Access-Control-Allow-Methods&#39;, &#39;GET,PUT,POST,DELETE,OPTIONS&#39;);
        res.header(&#39;Access-Control-Allow-Headers&#39;, &#39;Content-Type, Authorization, Content-Length, X-Requested-With&#39;);
          
        // intercept OPTIONS method
        if (&#39;OPTIONS&#39; == req.method) {
          res.send(200);
        }
        else {
          next();
        }
    };

and:

    app.configure(function () {
      app.use(express.bodyParser());
      app.use(express.methodOverride());
      app.use(app.router);
      app.use(allowCrossDomain);
      app.use(express.static(path.join(application_root, &quot;public&quot;)));
      app.use(express.errorHandler({ dumpExceptions: true, showStack: true }));
    });

From the Chrome console I get these headers:

Request URL:http://furious-night-5419.herokuapp.com/api/search?uri=http%3A%2F%2Flocalhost%3A5000%2Fcollections%2F1%2Fdocuments%2F1

Request Method:OPTIONS

Status Code:200 OK

Request Headers

    Accept:*/*
    Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
    Accept-Encoding:gzip,deflate,sdch
    Accept-Language:en-US,en;q=0.8
    Access-Control-Request-Headers:origin, x-annotator-auth-token, accept
    Access-Control-Request-Method:GET
    Connection:keep-alive
    Host:furious-night-5419.herokuapp.com
    Origin:http://localhost:5000
    Referer:http://localhost:5000/collections/1/documents/1
    User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5

Query String Parameters

    uri:http://localhost:5000/collections/1/documents/1

Response Headers

    Allow:GET
    Connection:keep-alive
    Content-Length:3
    Content-Type:text/html; charset=utf-8
    X-Powered-By:Express

Does this look like a lack of proper headers being sent by the API application? 

Thanks.

Allow CORS REST request to a Express/Node.js application on Heroku

When I do &#39;open .profile&#39; in the terminal I have the following:

    export PATH=$PATH:/usr/local/git/bin 

Now I installed node.js for Mac and it says, 

    

&gt; Make sure that /usr/local/bin is in your $PATH.

How can I add `/usr/local/bin` to export `PATH=$PATH:/usr/local/git/bin`?


How to add /usr/local/bin in $PATH on Mac

New to Node.js and Express, I am trying to understand the two seems overlapping concepts, routes vs controller.

I have seen examples that simple does app.js + routes/*, this seems to be sufficient to route various requests needed. 

However, I also see people talking about using controllers, and some that implies a more formal MVC model (???).

Would be great if someone can help me clear this mystery, and if you have a good example for setting up controller in Node.js + Express framework that will be great!

Thanks,

Node.js + Express: Routes vs controller

We&#39;re currently developing a website (TYPO3 under Apache) for a customer that is supported by a node.js/socket.io application that provides realtime updates to the content served from the CMS.

As this is our first node.js project I don&#39;t have any best practices to go by when it comes to &#39;the perfect setup&#39; so I&#39;ve spent some time researching deployment techniques.

A couple of questions remain for me to achieve a good setup which:

 1. **Is easy for the customer to deploy**. This is very important because our website will be integrated in their &#39;live&#39; TYPO3 installation which serves an abundance of websites and is running on servers which aren&#39;t managed by the customer but another (centralized) organization which makes support calls and server changes a slow process.

 2. **Should be easy to update.** As mentioned requesting restarts and making server changes is a slow process, so idealy the node installation should restart / update when it receives changes that are pushed onto the live installion using `git`.

**Deployment**

The [general consensus][1] seems to be to use `forever` when it comes to deploying node applications to keep them running. I&#39;ve tested `forever`, and it seems to work fine when installed by `npm install forever -g` (global). This would require external assistance to globally install on the live environment though, so I&#39;d prefer to have it running from the application&#39;s `node_modules` directory, but I haven&#39;t been able to create a solid wrapper to do so.

Additionally, `forever` works fine, but it has to be started manually. What would be the best approach to ensure that it gets started on server boot and keeps running? 
  
  - A simple `init.d` script?
  - Writing a watchdog wrapper?
  - A TYPO3 scheduler task that checks `forever` status?  

**Rapid development / Restart on update**

We&#39;re currently still in the development stage of the project and every time I make changes to the node.js application I manually restart `node` or `forever`. This works, but is far from ideal.
There are several smaller `npm` modules that check for file modifications and restart `node` upon detected changes, like:

 - [Nodemon][2]
 - [Node.js Supervisor][3]
 - [Bounce][4]
 - [Nodules][5] (which doesn&#39;t require restarting node, so might be easier to combine with `forever`)
 - [Up][6] 

Does anyone have experience with any of these?

**Update: Why don&#39;t you just use Cluster?**

The [Cluster module][7] provides similar functionality through the [reload][8] mechanism, but [doesn&#39;t work with Node 0.5+][9]. The [core Cluster module (Node 0.6+)][10] that replaced it doesn&#39;t have all these features but only provides clustering. Which in turn [doesn&#39;t play well with socket.io][11]. At least [not without using Redis][12] (which is a problem for us, because we can&#39;t force another prereq service to the customer).  

--

Obviously I&#39;m trying to find the most stable solution that combines an update-restarter with `forever` before handing over the project to the customer and I&#39;m really hoping anyone has produced a proven combination of techniques.
 


  [1]: https://stackoverflow.com/questions/4681067/how-to-deploy-node-js
  [2]: http://remysharp.com/2010/10/12/nodejs-rapid-development-nodemon/
  [3]: http://fgnass.posterous.com/nodejs-supervisor
  [4]: https://github.com/weepy/bounce
  [5]: https://stackoverflow.com/a/2929366/813718
  [6]: https://github.com/LearnBoost/up
  [7]: https://github.com/LearnBoost/cluster
  [8]: http://learnboost.github.com/cluster/docs/reload.html
  [9]: https://github.com/kriszyp/multi-node/issues/14
  [10]: http://nodejs.org/api/cluster.html
  [11]: https://github.com/LearnBoost/cluster/issues/95
  [12]: https://stackoverflow.com/questions/8395407/using-socket-io-with-cluster

Content Type	Original Author	Original Content on Stackoverflow
Question	MaiaVictor	View Question on Stackoverflow
Solution 1 - Javascript	user1106925	View Answer on Stackoverflow

What is the node.js equivalent of window["myvar"] = value?

Javascript Problem Overview

Javascript Solutions

Solution 1 - Javascript

Scrollbar without fixed height/Dynamic height with scrollbar

Add onClick event to document.createElement("th")

Attributions