14 Matching Annotations
  1. Feb 2019
    1. Top Reasons Why to Use Node.js for your E-commerce Business

      The arrival of E-commerce has changed how we shop today in our daily lives. Customers are seen buying on social media channels, Mobile apps, and websites. A set of heavy lighting goes behind an instinctive e-commerce website development that is described by the technical expertise that let into building it.

  2. Oct 2018
  3. Sep 2018
  4. Oct 2017
    1. healthcare roles, yet thereis a considerable amount of conversations from healthcare providers to average consumers,and from average consumers to media

      these are node attributes. I wonder how they derived them from twitter. Hopefully this will be spelled out in the methods.

  5. Sep 2017
    1. other network includes climate change deniers.

      What a great way of using SNA to compare two competing ways of knowing. How would you collect data to show the different flow of information through these networks? What what would you be looking for? What would the node be? The link?

  6. Jul 2017
    1. The npm client installs dependencies into the node_modules directory non-deterministically. This means that based on the order dependencies are installed, the structure of a node_modules directory could be different from one person to another. These differences can cause “works on my machine” bugs that take a long time to hunt down.

      This is why you should version control your package-lock.json.

  7. Mar 2017
    1. My idea of the consummate outsider is architect

      If he is an architect he is not really an outsider but he can be an outsider within a group - a possible point of connection to other groups....

    1. Star-hopping I start thinking about how I navigate the blogs, how I navigate Twitter, how I smile when I click on recognisable avatars.

      navigation. mapping nodes

    2. to my students (they are unaware of that for the moment unless the one Tweep has done his job for the masses and sent it viral in Clermont Ferrand STAPS).

      connection individual witness

  8. May 2016
    1. [Service] ExecStart=[node binary] /home/srv-node-sample/[main file] Restart=always StandardOutput=syslog StandardError=syslog SyslogIdentifier=node-sample User=srv-node-sample Group=srv-node-sample Environment=NODE_ENV=production [Install] WantedBy=multi-user.target
  9. Jun 2015
    1. Simply: require('child_process').spawn('vim', ['test.txt'], {stdio: 'inherit'}); If there is nothing left in the Node.js event loop when vim exits, then node will exit automatically as well. Or, if you need to guarantee node will exit when vim does: var vim = require('child_process').spawn('vim', ['test.txt'], {stdio: 'inherit'}); vim.on('exit', process.exit); As for closing the node application before vim exits, that's not really possible because vim inherits standard input/output/error streams from the spawning process (node) which are destroyed when node exits.