Node. JS – JS Node Rotating Header Image

Node.js

Dec 26th, 2011
by mgin.
Comments are off for this post

JS Node

This know-how, called Node.js, is being hailed as “the new Ruby on Rails” by some within the developer community. However it’s not a magic bullet, nor is it acceptable for all programming scenarios.

nodejs95 Node.js

Node.js

Joyent, an SF-primarily based cloud software program company, is sponsoring the growth and growth of JS Node. It employs Node.js creator Ryan Dahl, hosts occasions and creates tools for the growing Node.js community. Not too lengthy ago, Mashable visited Joyent to see demos from three startups that are utilizing Node to construct internet and cellular apps for consumers.

Within the process, we learned quite a bit about how and why JS Node works for the actual-time internet – and the way Node is altering the way the developer community creates the Internet as we all know it.

What Makes Node.js Totally different

Node.js had a watershed year in 2010, and it’s shaping as a lot as be as popular as Ruby on Rails among developers. For the explanation that framework was constructed for the generally used JavaScript, the obstacles to entry are remarkably low, and the reasons for choosing Node.js to construct apps – particularly low-latency, real-time apps – are increasingly compelling.

Then there’s the community. The Ruby community has been criticized for being unique and harsh. The JS Node group offers a welcome distinction and embodies the spirit of many other open-supply communities. Once more, the framework’s JavaScript roots implies that it appeals to the less hacker-ish internet designer who may be dabbling in web app growth as a lot because it appeals to longtime, hardcore hackers who simply need a better option to construct actual-time apps.

Why choose JS Node?

We asked each of the three startups giving demos at Joyent:

nodejs9 Node.js

JS Node

The frequent knowledge among many developers is that there is not any single right language or framework that ought to and must be used for all web apps. However based mostly on what we heard from these startups, Node.js is increasingly being seen as a “greatest answer” for a sure kind of application.

In line with Tom Hughes-Croucher, a recent Joyent rent who’s writing the primary O’Reilly guide on Node, “JS Node has popularized event-driven programming.” With event-driven programming, Hughes-Croucher explains, “The actual amount of assets you utilize is much smaller, and you can get much more out of fewer servers.”

Node is all about making occasion-driven, low-latency, concurrent apps. Erlang, the language that powers Facebook’s chat server, makes use of the same model. Tornado, a concurrent server for Python that powers FriendFeed, was an try at this, too. However Node.js has one advantage over technologies like Erlang and Tornado: “None of that was too accessible,” says Hughes-Croucher. “Node takes a language people know very nicely – Javascript – and makes it out there to do server programming, as well.”

In traditional languages and frameworks, the communication contained in the app between the online server and the database is essentially the most time-intensive part of the transaction. JS Node makes a much smaller footprint on your web server. It allocates internet server resources on an as-wanted basis, not pre-allocating a large chunk of resources for every user. For instance, Apache might assign 8MB to a person, while Node assigns 8KB.

“The finest way that Node.js is more environment friendly on servers is by not allocating resources to things whereas it waits,” says Hughes-Croucher. “Say it’s a should to talk to the database, and that’s going to take 50ms to respond. Instead of assigning the entire processing sources for that 50ms wait, it simply makes use of a placeholder. When the database responds, then it allocates the resources needed to process. That means it’s completely doable to do much more requests directly, since you solely allocate the server sources when it’s worthwhile to use them, not when you are ready on databases.”

Node.js’s Explosive Development

Not like PHP or Ruby, Node.js has yet to appear as the technological face of a preferred, mass-adopted net service like Twitter, WordPress or Facebook.

Rather, Node took off in the imaginations of programmers, organically changing into the quirky new tech that was on the tip of every tongue. First, devs asked in the occasion you’d heard of it; then, they started asking if you happen to’d tried it or constructed something with it.

As you’ll find a way to see from these GitHub reviews, both the number of committers and the variety of commits to Node.js core actually took off, and there are not any signs of Node’s development slowing down in the dev community.

Commits and committers to Node.js on GitHub peaked in the fall of 2010, but developers’ conversations round Node.js have actually simply began to pick up steam for the explanation that beginning of 2011. Right here’s a graph exhibiting Twitter conversations around Node.js; you’ll discover a number of spikes all through the fall of 2010, and extra constant conversations occurring in 2011.

nodejs92 Node.js

Nodes. JS

“If you occur to have a look at Rails and Node on GitHub and evaluate the site visitors,” says Hughes-Croucher, “Rails had 270,000 views over the previous three months. Node has 325,000, and it’s solely going up… it’s exploding.”

There have been “it” applied sciences previously, and the current vogue is Ruby on Rails. So what makes devs think JS Node is the inheritor apparent?

“Node is going to change into the subsequent massive factor for just a few causes,” said Hughes-Croucher. “Everyone wants to do way more highly effective apps – issues like Google Instantaneous and Facebook. People are expected to help tens of millions of users on a ton of gadgets in actual time. These are the expectations individuals have of purposes now. And should you did that with conventional frameworks, it might take endlessly, and the hardware would cost hundreds of thousands of dollars.

“The purpose of Node.js is that it’s actually quick, it’s very easy to scale, and the Javascript facet means it’s very easy to build.”

Node.js  for Real-Time Voice

Igal Perelman is the VP of product for Voxer, an iOS app that aims to “make audio attractive again.” It functions a bit like a walkie-talkie, a bit like a gaggle IM app and a bit like a social/location client app.

“There’s a large reason why children love to make use of walkie-talkies. It’s fun and quick,” stated Perelman. “We took that basic use case and improved it a lot.”

The user pushes a button, begins speaking, and the message is instantly sent to the app person on the opposite end. Both parties can pay attention and talk simultaneously. Chat requests come through as push notifications, permitting the customers to resolve on whether or not or to not be a component of the chat.

Users may re-listen to messages in case they want clarification or missed a half of a message, like rewinding a video. One other cool feature: The app helps group chats with limitless numbers of participants.

Finally, JS Node solely free.

Voxer uses Node.js because the low latency allows for close to-immediate transfer of audio data. Says Perelman: “Node.js was very crucial to this, as a result of the audio needed to be live. And Node allows us to keep up numerous connections with very low latency. It was a fairly easy decision.”

Voxer’s VP of expertise, Matt Ranney, informed us (via the app itself, of course), “This is our third iteration trying to do live voice. We first tried C++ for performance causes, but it surely was too sophisticated, too laborious to wrangle. Next, we chose Python. It was great, however sadly, the Python digital machine is extremely slow.

“So we’ve gone to the opposite extreme. In our third version, we’ve performed it in JS Node, and we’ve the perfect of both worlds. We’ve got the high-level language of Javascript and the excessive performance of the [Google's V8 JavaScript engine's] digital machine.”

Node.js for Gaming

One of the hackathons we adopted this year was Node.js Knockout, a forty eight-hour contest to see who in the world can build the perfect, most full, most fascinating Node apps on a really tight deadline.

The popularity winner for the 2010 contest was Scrabb.ly, a massively multiplayer on-line version of Scrabble. The game plays in actual time, and the map of all of the tiles is sprawling to gargantuan proportions.

The crew built the sport in two days and has since made an organization out of the project.

On the flipside, “Rails Rumble [a comparable, Ruby-on-Rails-flavored hackathon] has been round for 4 or five years, and only one firm has come out of it,” says Fortnight Labs and Node.js Knockout co-founder Gerad Suyderhoud. “We had an organization in our first year. Because Node.js is such an awesome expertise for real-time net apps, you see a lot more games, so the results are a lot more fun.” The subsequent Node Knockout is in August 2011.

Suyderhoud and co-founder Visnu Pitiyanuvath’s entry in the 2009 Rails Rumble was Lazeroids, however they found that constructing a real-time sport in RoR was “too hard.”

nodejs8 Node.js

Node.JS Tutorial

In terms of real-time video games, says Suyderhoud, “There’s really not lots that’s competing with [Node]. The other applied sciences simply aren’t nearly as good at doing actual time. They’re backed in older frameworks. Node.js was designed from the ground up for real time and to be easy to use. Other applied sciences would take ceaselessly to do the same things.”

“You may have this giant ecosystem of Javascript that’s excellent for real time,” he adds.

And as far as group is anxious, Suyderhoud says, “it’s wonderful how inclusive it is. I’ve by no means seen such good support. For Node.js Knockout, it was some people’s first time utilizing JS Node. We didn’t present numerous help, however we acquired actually lucky. A lot of people who had no vested interest and were not participants stepped up and helped people solve their problems over the weekend, in chat channels and over Twitter. I was definitely not expecting that.”

JS Node for Collaboration

Mockingbird is more a device for internet designers than a true client app, and it permits devs and designers to quickly create wireframes. The interesting factor about Mockingbird is that this Node.js app is already making severe cash for its creators.

Principally, Mockingbird is a instrument for collaborative drawing and actual-time communication between designers and clients. It took the founders just months to take the app from concept to a working beta.

“We’ve been round since November of 2009 and launched our paid product November 2010,” says CTO and co-founder Saikat Chakrabarti. “We’re doing much better than we thought. We thought we’d be struggling entrepreneurs for a really lengthy time, but we’re very a lot in the green.”

The app presently has 60,000 users and hosts more than one hundred,000 projects.

Says Chakrabarti: “I attempted to do the app in Twisted and Tornado at the time, and Node.js was by far the simplest… Lots of people and corporations are very invested in this.”

JS Node for the Future

Time will show whether Node.js is that next big thing, but one factor was agreed upon by all parties at this roundtable demo session: Node.js needs a Twitter, a Fb or some other large, consumer-friendly, mass-adopted app to make the mainstream tech neighborhood take notice.

However, as soon as center managers get wind of JS Node, it runs the risk of developing a bubble. An employment bubble would certainly be followed by an employment crash, which might possible be perceived as the “downfall of Node.js.”

A misunderstanding of the know-how can be a risk. Former Twitter engineer Alex Payne’s claim that Ruby was sluggish continues to haunt basic conversations about Ruby to this day.

It’s not our intention to inflate anybody’s expectations of JS Node. And we’re definitely not advocating its use for all programming projects. Nevertheless, we do suppose that Node.js is an attention-grabbing, accessible and efficient expertise for real-time functions, and we’d love to see what comes of this framework.

Post Footer automatically generated by wp-posturl plugin for wordpress.

Posted in: Node. JS.
Tagged: · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · ·

Node.js Hello World Tutorial Part 1

Feb 1st, 2012
by mgin.
Comments are off for this post

This tutorial guides you through installing node.js, including the creation of a easy hey world http server.

Installation
Initially: You should run a *nix operating system so as to use node.js at this point. Linux and OSX are really useful, however you also needs to be able to use FreeBSD and cygwin (on home windows). A full home windows port of node.js is in the works, but it is not but prepared for public usage.

nodejs7 Node.js Hello World Tutorial Part 1

Node.JS Tutorial

The most common technique to set up node.js is to immediately compile it from the downloaded source code. There are also various packages obtainable for various package managers, but since their replace frequency varies, I recommend installing from source.

You will get the most recent source code from nodejs.org. Use the instructions below to obtain and set up v0.4.four:

$ wget http://nodejs.org/dist/node-v0.4.4.tar.gz
$ tar -xzf node-v0.4.4.tar.gz
$ cd node-v0.4.4.tar.gz
$ ./configure
$ sudo make install
Node.js itself has no external dependencies except common construct instruments in addition to pythons for the build system itself. On OSX it’s essential to set up XCode for this to work, and on Ubuntu you probably should run:

$ apt-get -y install construct-essential
The interactive node.js shell
If every thing worked, you should have the ability to invoke the interactive node.js shell like this:

$ node
> console.log(‘Hey World’);
Hey World
The interactive shell (also known as REPL) is a great place to test easy one liners, and can also be straight embedded into your node.js applications. In order to get out of it, simply press Ctrl + C.

The REPL additionally comes with many different nice features, most significantly tab auto-completion.

Your first program
Writing a node.js program is so simple as creating a new file with a ‘.js’ extension. For instance you would create a simple ‘hello_world.js’ file with the next content:

console.log(‘Whats up World’);After you’ve got saved the file, you possibly can execute it out of your terminal like so:

$ node hello.js
Hiya World
A hi there world http server
Now printing hiya world to a terminal is not all that exciting. Let’s take the subsequent step and write a program that responds to hello world by way of http. We’ll call the file ‘hello_http.js’ and put the following code into it:

var http = require(‘http’);var server = http.createServer(function(req, res) res.writeHead(200); res.end(‘Hello Http’););server.listen(8080);Now lets run this program from the terminal by typing:

$ node hello_http.js
The first thing you may notice is that this program, in contrast to our first one, does not exit proper away. That’s as a result of a node program will at all times run till it is certain that no further occasions are possible. In this case the open http server is the supply of events that may maintain things going.

Testing the server is so simple as opening a new browser tab, and navigating to the following url: http://localhost:8080/. As expected, you must see a response that reads: ‘Hey Http’.

Alternatively, you possibly can also open up a new terminal and use curl to check your server:

$ curl localhost:8080
Hey Http
Now let’s have a closer look at the steps concerned in our little program. In the first line, we embrace the http core module and assign it to a variable referred to as http. One can find more info on this in the subsequent part about the module system.

Next we create a variable known as server by calling http.createServer. The argument passed into this call is a closure that is called each time an http request comes in.

Finally we name server.listen(8080) to inform node.js the port on which we would like our server to run. If you wish to run on port 80, your program must be executed as root.

Now when you level your browser to ‘localhost:8080′, the connection closure is invoked with a req and res object. The req is a readable stream that emits ‘data’ occasions for every incoming piece of data (like a form submission or file add). The res object is a writable stream that’s used to send information again to the client. In our case we are merely sending a 200 OK header, as well as the physique ‘Hello Http’.

The module system
As a way to construction your program into totally different recordsdata, node.js offers you with a simple module system.

For example the approach, let’s create a brand new file referred to as ‘main.js’ with the next content material:

var hey = require(‘./hey’);hello.world();As you have probably guessed, the require(‘./good day’) is used to import the contents from one other JavaScript file. The initial ‘./’ indicates that the file is situated in the same listing ‘main.js’. Additionally word that you do not have to supply the file extension, as ‘.js’ is assumed by default.

So let’s go ahead and create our ‘hello.js’ file, with the next content material:

exports.world = perform() console.log(‘Hiya World’);What you notice right here, is that we’re assigning a property called ‘world’ to an object called ‘exports’. Such an ‘exports’ object is offered in each module, and it’s returned each time the require operate is used to incorporate the module. If we now go ahead and run our ‘main.js’ program, we will see the anticipated output:

$ node main.js
Hiya World
At this point it must also be mentioned that many node users are overwriting the exports object directly like so:

module.exports = operate() // …As you may need anticipated, this will instantly cause the require perform to return the assigned function. That is useful in the event you’re doing object oriented programming, the place each file exports the constructor of 1 class.

The following factor you want to know in regards to the module system is how it deals with require calls that do not embody a relative hint in regards to the location of the included file. Take for example:

var http = require(‘http’);What node.js will do in this case, is to first look if there is a core module named http, and since that is the case, return that directly. But what about non-core modules, reminiscent of ‘mysql’?

nodejs93 Node.js Hello World Tutorial Part 1

JS Node

var mysql = require(‘mysql’);On this case node.js will walk up the directory tree, shifting by way of each parent listing in turn, checking in each to see if there’s a folder called ‘node_modules’. If such a folder is discovered, node.js will look into this folder for a file referred to as ‘mysql.js’. If no matching file is found and the directory root ‘/’ is reached, node.js will give up and throw an exception.

At this level node.js additionally considers a further, mutable list of different include directories which are accessible through the require.paths array. Nonetheless, there’s intense debate about eradicating this function, so you might be probably better off ignoring it.

Last however not least, node.js also allows you to create an ‘index.js’ file, which signifies the primary embody file for a directory. So in the event you name require(‘./foo’), each a ‘foo.js’ file in addition to an ‘foo/index.js’ file can be thought-about, this goes for non-relative contains as well.

Post Footer automatically generated by wp-posturl plugin for wordpress.

Posted in: Node.JS Tutorials.
Tagged: · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · ·

Node.JS Package Manager

Feb 16th, 2012
by mgin.
Comments are off for this post

nodejs96 Node.JS Package Manager“Modules” in Node.js are just like libs in C or JAR files in Java. A module is usually a single file (or a group of recordsdata) that you just include in your code for added strategies and functionality. Node.js is partially compatible with the CommonJS securable module system, so there's a whole set of specifications on tips on how to create new modules. We gained't get into that here.

 As a substitute, right here's how one can embrace a module into your mission:

 var fooModule = require('foo');

 fooModule.someNewFunction();That's it! You call the global require() operate, and assign it to a variable. That variable then incorporates the exported members of the foo module.

This paradigm is essential to creating in Node.js, since all the core libraries are thought of modules, and have to be assigned on this way.

 You can even specify a sure directory to search for a module:

 var farAway = require('../../../bar');Technically, you don't even have to specify the .. listing change. Node.js all the time looks within the curent listing for a module. If it doesn't discover it, it walks up the directory, checking each parent, looking for both a file matching your module's identify (bar.js), or, a folder called node_modules that contains your file. If it could actually't find a file matching your module name by the time it hits the root listing ('/'), Node.js throws an exception.

 Now, the enjoyable half: there's a complete ecosystem of passionate third-party and open source developers creating their own modules for Node.js. The Node Bundle Manager, or npm, is designed to be each a source of finding modules to install, and a option to handle module dependencies inside your personal projects.

 Proper after putting in Node.js, you'll almost actually want to set up the npm command-line tool for managing packages. When you've done that, you can start shopping the npm registry to search out and set up new packages.

 Local and international Node.js installs

There's a distinction price pointing out once you first begin putting in packages. By default, npm installs any modules you want within the present listing it's called at. Thus, if you're engaged on a mission call theLatestAndGreatest, and you need to set up specific, the bundle is only relative to your project. For those who decide to work on a brand new undertaking in a distinct listing referred to as thisIsIt, you'll need to reinstall express once more via npm.

 To work around this, you can strive installing Node.js packages globally. You can do this by specifying the -g switch on the command prompt. This installs the module in a particular location that varies depending in your operating system. Any project you start can then safely require() modules.

Post Footer automatically generated by wp-posturl plugin for wordpress.

Posted in: Node.JS Modules.

Node.js support in Komodo IDE 7

Feb 16th, 2012
by mgin.
Comments are off for this post

nodejs94 Node.js support in Komodo IDE 7ActiveState has launched a major new model of the Komodo built-in development surroundings (IDE). The update, which is known as Komodo 7, introduces a number of helpful new options and support for additional programming languages.

Komodo is a high-finish business development device for programmers who work with scripting languages resembling Python and Ruby. It is particularly nicely-suited for growing large-scale Internet applications. It supports code completion and breakpoint debugging for a relatively broad number of programming languages.

Komodo is constructed on top of Mozilla’s Gecko rendering engine with the XUL user interface toolkit. A few of Komodo’s underlying structure is inherited from Firefox, including a wealthy add-on system. The core editing elements of Komodo IDE are developed as open source software and are shared with a free standalone editor called Komodo Edit that lacks the IDE’s debugger and different superior functionality.

A number of the major new features introduced in Komodo 7 embrace assist for actual-time collaborative modifying on code recordsdata, a brand new constructed-in profiling instrument for Python and PHP, a much-improved syntax checker, and the flexibility to synchronize your settings between computers. Alongside these new features, Komodo 7 additionally provides support for a number of new programming languages and frameworks, including CoffeeScript and Node.js.

I have never had a chance but to attempt all the new options, but I put the new Node.js performance to work during some palms-on testing. Komodo’s Node.js help isn’t as mature or sturdy as its dealing with of different languages but, nevertheless it nonetheless proved helpful for Node.js development.

The built-in debugging support for Node.js

The built-in debugging support for Node.js is fairly comprehensive and nicely done. Along with showing you the worth of your watch expressions whenever you hit a breakpoint, it can additionally show you a tree of all of the variables inside the current scope. You can increase knowledge buildings and objects to see their contents. Once you use the debugger to step into an expression, the IDE can discover and show the function you might have stepped into even if it is in another module.

Komodo’s newly improved syntax checker is helpful and very functional. It picked up errors in my JavaScript code, corresponding to unmatched parentheses and missing operators, nearly instantly. It can inform you the line and column and take you to the precise place whenever you click on the entry in the error panel.

Komodo’s code browser, which supplies you a visible overview of the capabilities, objects, and variables defined within the at the moment lively file, works relatively effectively with JavaScript. It isn’t as helpful as it could be for Node.js improvement, however.

Due to the occasion-primarily based nature of the framework, quite a lot of code in Node.js applications tends to be applied inside of callbacks. This means that you find yourself with numerous indistinguishable anonymous capabilities within the Komodo code browser. In circumstances the place you might have an nameless operate bound to an EventEmitter signal, I would desire to have the code browser present the event name. That situation aside, the code browser remains to be quite good for Node.js programming if you end up working with more typical JavaScript.

The foremost weak area for Node.js help in Komodo 7 is its code completion. With a purpose to get code completion on libraries, it’s a must to manually configure the IDE so that it knows the paths of third-party modules that you want to use. It’s supposed to have the ability to scan other recordsdata in your project by following the require statements, but it surely appeared to have difficulty doing so with the trivial challenge that I used for my testing.

There are a lot of other nice things about Komodo that I have not touched on in this article however are worthy of praise, corresponding to its deep extensibility, excellent Vim emulation mode, and thoughtfully unobtrusive approach to mission management. These traits and broad language assist are the the reason why we’ve got historically given Komodo our stamp of approval (we even included it in a gift guide once).

The brand new model builds on all of those strengths and continues to introduce helpful new functionality. The Node.js assist is a welcome addition, but nonetheless needs further work before it will be as strong as the IDE’s present help for different languages.

The Komodo IDE is currently accessible for $245 from ActiveState on sale. At that worth, it most likely is not going to be sensible for users who are just in search of a dedicated Node.js improvement environment. Komodo remains an excellent worth, nevertheless, for skilled developers who work on giant tasks and usually use several of the programming languages supported by the IDE.

Post Footer automatically generated by wp-posturl plugin for wordpress.

Posted in: Node.JS Modules.
Tagged: · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · ·

Node.js Hello World Tutorial Part 2

Feb 1st, 2012
by mgin.
Comments are off for this post

Utilizing EventEmitters
Node.js implements the observer sample using a class known as EventEmitter. Each time there may be an object that represents the supply of a number of sorts of occasions, node.js usually makes the underlaying class inherit from EventEmitter.

Using EventEmitter’s is fairly straight-forward. You may listen to a specific event by calling the ‘on()’ function on your object, offering the name of the event, in addition to a callback closure as the parameters. For instance:

var information = ”;req .on(‘knowledge’, perform(chunk) data += chunk; ) .on(‘end’, perform() console.log(‘POST information: %s’, knowledge); )As you can see, the on() perform also returns a reference to the thing it belongs to, permitting you to chain a number of of such occasion listeners.

Should you’re only interested in the first prevalence of an event, you should use the as soon as() operate instead.

nodejs4 Node.js Hello World Tutorial Part 2

Node. JS

Lastly, you possibly can take away event listeners by utilizing the removeListener function. Please be aware that the argument to this operate is a reference to the callback you are attempting to take away, not the identify of the occasion:

var onData = function(chunk) console.log(chunk); req.removeListener(onData);req.on(‘data’, onData);The instance above is actually identical to the once() function.

Subsequent Steps
Now that you realize your node.js fundamentals, you are in all probability finest off by writing a couple of little applications yourself. The most effective place to start out out is node’s api documentation, utilizing it as a supply of inspiration for something you need to play with.

Debugging node.js apps
There are a lot of methods to debug your node.js based mostly applications. Personally I favor to do as little debugging as doable, so I strictly comply with the recommendation of the test pushed growth guide.

Nevertheless, if you find yourself in a scenario where it is advisable locate a tough bug in an current purposes, here are just a few approaches that can help.

Utilizing console.log()
The best way to perceive a problem is by inspecting objects using console.log(). You’ll be able to either directly pass in objects as parameters:

var foo = bar: ‘foobar’;console.log(foo);Or you should use its sprintf()-like capabilities to format your debug output:

var foo = bar: ‘foobar’;console.log(‘Whats up %s, that is my object: %j’, ‘World’, foo);Using the node debugger
If console.log() is not your factor, otherwise you assume your drawback can be better analyzed utilizing breakpoints, the node’s constructed-in debugger is a great choice. You can invoke the debugger by simply calling:

$ node.js debug my_file.js
Work in progress, please come again later …

Utilizing the WebKit Inspector
Work in progress, please come back later …

Frameworks
If you’re new to node.js, you may not wish to re-invent the wheel on the subject of parsing POST requests, routing urls or rendering views. On this case, you in all probability want to use one of the fashionable internet frameworks. This part offers you a fast overview over the favored decisions, and my opinionated tackle them.

Express
At this point specific is probably the go-to framework for many node.js developers. It is relatively mature, and consists of the join (assume rack) middleware layer. Included in the bundle are routing, configuration, a template engine, POST parsing and plenty of other features.

Whereas categorical is a strong framework, it is at the moment addressing a a lot smaller scope than fullstack frameworks like Rails, CakePHP or Django. It’s extra akin to Sinatra, and sadly does not really make a big effort to distinguish itself from its Ruby roots into one thing that feels natural in JavaScript. Anyhow, wanting writing your personal framework, it is certainly an amazing choice at this point.

fab.js
You think you realize JavaScript? Suppose again. Originally inspired by jQuery’s chaining, fab.js has taken a very unconventional method of twisting JavaScript beyond most peoples brain capacity. Each perform returns another function, eliminating the need for method names altogether, whereas giving the resulting code a lisp-esque look & feel.

At this level I do not think about fab.js production-prepared, however if you’re nonetheless exploring the world of node.js, it’s best to absolutely strive it out at the very least once. If nothing else, fab.js reveals the world that JavaScript doesn’t have to repeat Ruby, Python or PHP in terms of net frameworks, and can go its own unique ways.

Internet hosting & Deployment
Quick & Soiled Deployment
If you have simply written your first node.js software, and you want to get it working as fast as attainable, that is how to do it:

1.Copy your program to the server you wish to run it on. For those who’re utilizing git, this in all probability simply means to clone the repository from another server or service like GitHub.

2.Assuming your challenge accommodates a ‘server.js’ file, navigate to the listing containing it, then sort:

$ display screen
$ node server.js
This invokes your ‘server.js’ program inside a so called display screen session. Display is a instrument that provides you with a shell that remains its state, even if you close the terminal app you used to login to your server.

So you can now safely shut your terminal app, and your ‘server.js’ will proceed running. If you wish to monitor it, you possibly can log into your server again, and kind:

$ display -r
It will reconnect you to the backgrounded shell running your program.

Nonetheless, this strategy is barely advisable for experimental deployments. In case your node functions crashes sooner or later, display won’t attempt to restart it, so don’t use this technique for production applications.

Post Footer automatically generated by wp-posturl plugin for wordpress.

Posted in: Node.JS Examples.
Tagged: · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · ·