EDIT: As of December 2018, this is no longer the correct way. See the other two answers.

&gt;! You need to symlink the nodejs executable to node `sudo ln -s &quot;$(which nodejs)&quot; /usr/local/bin/node` The reason for this is that when you do &quot;apt-get install node&quot;, it installs an unrelated package, so they had to choose a different name so it wouldn&#39;t conflict

While the accepted answer fixes the problem, the correct way to do that, at least with Debian Jessie and forward and Ubuntu 14.4 and forward[1] is to install **nodejs-legacy**:

    apt-get install nodejs-legacy

The reason is that Debian already had a package (node) providing */usr/bin/node*, and the nodejs *node* binary had to be installed into /usr/bin/nodejs.

The **nodejs-legacy** package provides a symbolic link from /usr/bin/nodejs to /usr/bin/node (and conflicts with the **node** package).

Source: [\[CTTE #614907\] Resolution of node/nodejs conflict][2] and [Debian bug #614907: node: name conflicts with node.js interpreter][3]



  [1]: http://packages.ubuntu.com/search?keywords=nodejs-legacy
  [2]: https://lists.debian.org/debian-devel-announce/2012/07/msg00002.html
  [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614907

It&#39;s better if you update to the latest node version

 1. sudo npm cache clean -f 
 2. sudo npm install -g n
 3. sudo n stable

I am trying to use the new Design TabLayout in my project. I want the layout to adapt to every screen size and orientation, but it can be seen correctly in one orientation.

I am dealing with Gravity and Mode setting my tabLayout as:

        tabLayout.setTabGravity(TabLayout.GRAVITY_CENTER);
        tabLayout.setTabMode(TabLayout.MODE_SCROLLABLE);

So I expect that if there is no room, the tabLayout is scrollable, but if there is room, it is centered.

From the guides: 

&gt; public static final int GRAVITY_CENTER Gravity used to lay out the
&gt; tabs in the center of the TabLayout.
&gt; 
&gt; public static final int GRAVITY_FILL Gravity used to fill the
&gt; TabLayout as much as possible. This option only takes effect when used
&gt; with MODE_FIXED.
&gt; 
&gt; public static final int MODE_FIXED Fixed tabs display all tabs
&gt; concurrently and are best used with content that benefits from quick
&gt; pivots between tabs. The maximum number of tabs is limited by the
&gt; view’s width. Fixed tabs have equal width, based on the widest tab
&gt; label.
&gt; 
&gt; public static final int MODE_SCROLLABLE Scrollable tabs display a
&gt; subset of tabs at any given moment, and can contain longer tab labels
&gt; and a larger number of tabs. They are best used for browsing contexts
&gt; in touch interfaces when users don’t need to directly compare the tab
&gt; labels.

So GRAVITY_FILL is compatible only with MODE_FIXED but, at is doesn&#39;t specify anything for GRAVITY_CENTER, I expect it to be compatible with MODE_SCROLLABLE, but this is what I get using GRAVITY_CENTER and MODE_SCROLLABLE

![enter image description here][1]



So it is using SCROLLABLE in both orientations, but it is not using GRAVITY_CENTER.

This is what I would expect for landscape; but to have this, I need to set MODE_FIXED, so what I get in portrait is:

![enter image description here][2]

Why is GRAVITY_CENTER not working for SCROLLABLE if the tabLayout fits the screen?
Is there any way to set gravity and mode dynamically (and to see what I am expecting)?

Thank you very much!

EDITED: This is the Layout of my TabLayout:

    &lt;android.support.design.widget.TabLayout
        android:id=&quot;@+id/sliding_tabs&quot;
        android:layout_width=&quot;match_parent&quot;
        android:background=&quot;@color/orange_pager&quot;
        android:layout_height=&quot;wrap_content&quot; /&gt;


  [1]: http://i.stack.imgur.com/pXj3K.png
  [2]: http://i.stack.imgur.com/nBwCh.png

Android Support Design TabLayout: Gravity Center and Mode Scrollable

I&#39;m looking for some pros and cons of whether to go with Marathon and Chronos, Docker Swarm or Kubernetes when running Docker containers on DC/OS. 

For example, when is it better to use Marathon/Chronos than Kubernetes and vice versa? 

Right now I&#39;m mostly into experimenting but hopefully we&#39;ll start using one of these services in production after the summer. This may disqualify Docker Swarm since I&#39;m not sure if it&#39;ll be production ready by then. 

What I like about Docker Swarm is that it&#39;s essentially just &quot;Docker commands&quot; and you don&#39;t have to learn something completely new. We&#39;re already using `docker-compose` and that will work out of the box with Docker Swarm (at least in theory) so that would be a big plus. My main concern with Docker Swarm is if it&#39;ll cover all use cases required to run a system in production.

Marathon vs Kubernetes vs Docker Swarm on DC/OS with Docker containers

I have installed nodejs using:

    apt-get install nodejs

Then i have installed npm using:

    apt-get install npm

And then i have installed forever using:

    npm install forever -g

Now i go to my project `/var/www/myproject`

and attempt to run `forever start server.js`

then i get the following message:

    /usr/bin/env: node: No such file or directory


Can anyone tell me whats going on?



Node forever /usr/bin/env: node: No such file or directory

I have installed nodejs using:
<pre><code class="hljs language-arduino">apt-get install nodejs
</code></pre>
Then i have installed npm using:
<pre><code class="hljs language-arduino">apt-get install npm
</code></pre>
And then i have installed forever using:
<pre><code class="hljs">npm install forever -g
</code></pre>
Now i go to my project <code>/var/www/myproject</code>
and attempt to run <code>forever start server.js</code>
then i get the following message:
<pre><code class="hljs language-yaml">/usr/bin/env: node: No such file or directory
</code></pre>
Can anyone tell me whats going on?

**Q:** Is it possible to change the the context in which npm runs scripts?

What I want to is the following:

&lt;!-- language: lang-js --&gt;

    &quot;scripts&quot;: {
       &quot;test&quot;: &quot;gulp mocha&quot;,
       &quot;pre-install&quot;: &quot;./deps/2.7/cpython/configure --prefix=$(pwd)/build --exec-prefix=$(pwd)/build &amp;&amp; make -C deps/2.7/cpython &amp;&amp; make -C deps/2.7/cpython install&quot;,
       &quot;install&quot;: &quot;node-gyp rebuild&quot;
    },

Obviously `cd deps/2.7/cpython/ &amp;&amp; ./configure` would work on UNIX-like systems but not on windows. 

**Why:** The root of the problem is, that the `configure` command of the python repo outputs files into the directory where it is called. The files however are build relevant for `make` and `make install` which look for the files in the directory of the repo.

In this case I can&#39;t change the `Makefile` since the build process of Python is understandably complex.

**Alternative:** The alternative is probably to write some `install.js` and use node&#39;s OS independent API and some `child_process.exec()`, which I am probably gonna do. However, not leaving *npm* would be really nice.

Change working directory for npm scripts

My question concerns an existing library that I wish to publish as an NPM module. The library is already in use, and currently `require`d via the local file system.

**How can I specify the root directory of my module&#39;s files?**

If I have a structure like:

    .
    ├── package.json
    ├── src
    |   ├── js
    |   └────── lib
    |   └───────── my
    |   └───────────── thing.js
    |   └───────────── that.js

**How do I specify that the root of my module, and accessible files is `src/js/lib/my/`?**

I would like to use as follows from an outside project:

    var thing = require(&#39;my/thing&#39;),
        that = require(&#39;my/that&#39;);

I saw the `&quot;files&quot;` property in package.json, is this the right way to go?

Root directory in package.json

    console.log(process.env.COLUMNS)

Yields `undefined`, although,

    $ echo $COLUMNS

Outputs as expected:

    78

I have been trying running Node like this `env node myprog.js`, still `undefined`. What&#39;s wrong with me or any other way to know the width of terminal? (For nice formatting of some output data).


Get width of terminal in Node.js

This works:

    import app from &#39;./../app.js&#39;;

But this doesn&#39;t:

    import app from path.join(process.cwd(), &#39;app&#39;);

I&#39;m Getting:

    SyntaxError: /path/file.js: Unexpected token (5:16)
    &gt; 5 | import app from path.join(process.cwd(), &#39;app&#39;);
        |                 ^


It is possible (and/or how) to use &quot;dynamic&quot; paths? (not hardcoding the path or rely in relative paths).

Importing modules using ES6 syntax and dynamic path

I&#39;m attempting to load an RSA private key into my nodejs application using environment variables, but the newlines seem to be being auto-escaped.

For the following, assume that the ```PRIVATE_KEY``` env var is set to the following (not my actual key):

    PRIVATE_KEY=&quot;-----BEGIN RSA PRIVATE KEY-----\nMIICXAIBAAKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe4eCZ0FPqri0cb2JZfXJ/DgYSF6vUp\nwmJG8wVQZKjeGcjDOL5UlsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5\n1s1SPrCBkedbNf0Tp0GbMJDyR4e9T04ZZwIDAQABAoGAFijko56+qGyN8M0RVyaRAXz++xTqHBLh\n3tx4VgMtrQ+WEgCjhoTwo23KMBAuJGSYnRmoBZM3lMfTKevIkAidPExvYCdm5dYq3XToLkkLv5L2\npIIVOFMDG+KESnAFV7l2c+cnzRMW0+b6f8mR1CJzZuxVLL6Q02fvLi55/mbSYxECQQDeAw6fiIQX\nGukBI4eMZZt4nscy2o12KyYner3VpoeE+Np2q+Z3pvAMd/aNzQ/W9WaI+NRfcxUJrmfPwIGm63il\nAkEAxCL5HQb2bQr4ByorcMWm/hEP2MZzROV73yF41hPsRC9m66KrheO9HPTJuo3/9s5p+sqGxOlF\nL0NDt4SkosjgGwJAFklyR1uZ/wPJjj611cdBcztlPdqoxssQGnh85BzCj/u3WqBpE2vjvyyvyI5k\nX6zk7S0ljKtt2jny2+00VsBerQJBAJGC1Mg5Oydo5NwD6BiROrPxGo2bpTbu/fhrT8ebHkTz2epl\nU9VQQSQzY1oZMVX8i1m5WUTLPz2yLJIBQVdXqhMCQBGoiuSoSjafUhV7i1cEGpb88h5NBYZzWXGZ\n37sJ5QsW+sJyoNde3xH8vdXhzU7eT82D6X/scw9RZz+/6rCJ4p0=\n-----END RSA PRIVATE KEY-----&quot;

If I call ```console.log``` directly with the preceding string, I get the following as output:

    -----BEGIN RSA PRIVATE KEY-----
    MIICXAIBAAKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe4eCZ0FPqri0cb2JZfXJ/DgYSF6vUp
    wmJG8wVQZKjeGcjDOL5UlsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5
    1s1SPrCBkedbNf0Tp0GbMJDyR4e9T04ZZwIDAQABAoGAFijko56+qGyN8M0RVyaRAXz++xTqHBLh
    3tx4VgMtrQ+WEgCjhoTwo23KMBAuJGSYnRmoBZM3lMfTKevIkAidPExvYCdm5dYq3XToLkkLv5L2
    pIIVOFMDG+KESnAFV7l2c+cnzRMW0+b6f8mR1CJzZuxVLL6Q02fvLi55/mbSYxECQQDeAw6fiIQX
    GukBI4eMZZt4nscy2o12KyYner3VpoeE+Np2q+Z3pvAMd/aNzQ/W9WaI+NRfcxUJrmfPwIGm63il
    AkEAxCL5HQb2bQr4ByorcMWm/hEP2MZzROV73yF41hPsRC9m66KrheO9HPTJuo3/9s5p+sqGxOlF
    L0NDt4SkosjgGwJAFklyR1uZ/wPJjj611cdBcztlPdqoxssQGnh85BzCj/u3WqBpE2vjvyyvyI5k
    X6zk7S0ljKtt2jny2+00VsBerQJBAJGC1Mg5Oydo5NwD6BiROrPxGo2bpTbu/fhrT8ebHkTz2epl
    U9VQQSQzY1oZMVX8i1m5WUTLPz2yLJIBQVdXqhMCQBGoiuSoSjafUhV7i1cEGpb88h5NBYZzWXGZ
    37sJ5QsW+sJyoNde3xH8vdXhzU7eT82D6X/scw9RZz+/6rCJ4p0=
    -----END RSA PRIVATE KEY-----

You can see that the newline chars are being respected. However, if I call ```console.log(process.env[&quot;PRIVATE_KEY&quot;])```, the output contains the `\n` literal instead of actual newlines:

    -----BEGIN RSA PRIVATE KEY-----\nMIICXAIBAAKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe4eCZ0FPqri0cb2JZfXJ/DgYSF6vUp\nwmJG8wVQZKjeGcjDOL5UlsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5\n1s1SPrCBkedbNf0Tp0GbMJDyR4e9T04ZZwIDAQABAoGAFijko56+qGyN8M0RVyaRAXz++xTqHBLh\n3tx4VgMtrQ+WEgCjhoTwo23KMBAuJGSYnRmoBZM3lMfTKevIkAidPExvYCdm5dYq3XToLkkLv5L2\npIIVOFMDG+KESnAFV7l2c+cnzRMW0+b6f8mR1CJzZuxVLL6Q02fvLi55/mbSYxECQQDeAw6fiIQX\nGukBI4eMZZt4nscy2o12KyYner3VpoeE+Np2q+Z3pvAMd/aNzQ/W9WaI+NRfcxUJrmfPwIGm63il\nAkEAxCL5HQb2bQr4ByorcMWm/hEP2MZzROV73yF41hPsRC9m66KrheO9HPTJuo3/9s5p+sqGxOlF\nL0NDt4SkosjgGwJAFklyR1uZ/wPJjj611cdBcztlPdqoxssQGnh85BzCj/u3WqBpE2vjvyyvyI5k\nX6zk7S0ljKtt2jny2+00VsBerQJBAJGC1Mg5Oydo5NwD6BiROrPxGo2bpTbu/fhrT8ebHkTz2epl\nU9VQQSQzY1oZMVX8i1m5WUTLPz2yLJIBQVdXqhMCQBGoiuSoSjafUhV7i1cEGpb88h5NBYZzWXGZ\n37sJ5QsW+sJyoNde3xH8vdXhzU7eT82D6X/scw9RZz+/6rCJ4p0=\n-----END RSA PRIVATE KEY-----

I&#39;ve been trying to find more information online about how node processes environment variables with no luck. How do I load this key via env vars while maintaining newline characters? If that&#39;s not possible, how can I restore them?

Content Type	Original Author	Original Content on Stackoverflow
Question	Marc Rasmussen	View Question on Stackoverflow
Solution 1 - node.js	chedabob	View Answer on Stackoverflow
Solution 2 - node.js	Clément Schreiner	View Answer on Stackoverflow
Solution 3 - node.js	Shantanu	View Answer on Stackoverflow

Node forever /usr/bin/env: node: No such file or directory

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Solution 2 - node.js

Solution 3 - node.js

Marathon vs Kubernetes vs Docker Swarm on DC/OS with Docker containers

Android Support Design TabLayout: Gravity Center and Mode Scrollable

Attributions