Download as PDF, PPTX
![37 perforce.com
What did we learn?
• Node.js is a language that focuses on concurrency and unified
development
• Dependencies (modules) and builds are assisted through npm
• Node is asynchronous by default
• Many IDEs exist for Node.js, and we have focused on VSCode
• Node projects should be initialized using ”npm init”
• Modules can be installed with “npm install –save [module]”
• Projects are built from package.json in other environments with “npm
install”
• Modules are included as variables in a project using the “require”
directive](https://image.slidesharecdn.com/getting-started-with-node-190822185636/85/Getting-Started-with-Node-js-37-320.jpg)
![37 perforce.com
What did we learn?
• Node.js is a language that focuses on concurrency and unified
development
• Dependencies (modules) and builds are assisted through npm
• Node is asynchronous by default
• Many IDEs exist for Node.js, and we have focused on VSCode
• Node projects should be initialized using ”npm init”
• Modules can be installed with “npm install –save [module]”
• Projects are built from package.json in other environments with “npm
install”
• Modules are included as variables in a project using the “require”
directive](https://image.slidesharecdn.com/getting-started-with-node-190822185636/75/Getting-Started-with-Node-js-37-2048.jpg)
More Related Content
Similar to Getting Started with Node.js
Getting Started with Node.js
- 1. Getting Started withNode.js JUSTIN REOCK | CHIEF ARCHITECT | OPENLOGIC BY PERFORCE
- 2. Who is thisnerd?
- 3. 3 perforce.com Justin Reock ChiefArchitect OpenLogic by Perforce Presenter Justin has over 20 years’ experience working in various software roles and is an outspoken free software evangelist, delivering enterprise solutions and community education on databases, integration work, architecture, and technical leadership. He is currently the Chief Architect at OpenLogic by Perforce.
- 4. 4 perforce.com GitHub Repofor Demos • https://github.com/jreock/ getting-started-with- node.js • ColorsModule will require an “npm install” – but don’t worry I’ll teach you how to do it!
- 5.
- 6. What are wegoing to solve?
- 7.
- 8. 8 perforce.com Asychronous Processing •No one likes the spinning wheel of doom hope! • Node.js is inherently asynchronous, blocking actions only when it absolutely needs to • This is ideal for our new(ish) world of parallel compute, distributed compute, microservices, etc… • Built on industry standards and vetted against thousands of production systems
- 9.
- 10. 10 perforce.com A LongTime Ago… Backend Silo Front End Silo Backend Servers Front End Servers App
- 11. 11 perforce.com Behold, TheFuture! DevOps Team App Farm App Node allows us to code our front end and our backend using a single language
- 12. 12 perforce.com Node.js Overview •Created by Ryan Dahl in 2009 to address concurrency issues. • Dahl famously “built it over the weekend…” • Built on Chrome’s V8 JavaScript engine. • Single-threaded asynchronous event driven JavaScript framework. In- progress tasks can easily be checked for completion. • Vertical scaling can be achieved by adding CPU cores and adding a worker to each core. This means resources can be shared (via the cluster module and child_process.fork(…)). • Using JavaScript on the browser as well as the server minimizes the mismatch between the environments. Example: Form validation code does not have to be duplicated on both client and server. • Node.js objects maintain a list of registered subscribers and notifies them when their state changes (‘Observer’ design pattern).
- 13. 13 perforce.com Why reinventthe wheel? • npm is the node (sic) package manager for Node.js. • npm enables JavaScript developers to share code to solve common problems promoting reuse. This allows developers to take advantage of the expertise of a large community. • Very active and vibrant community: As of February 2017, there were nearly 400,000 total packages on npm.
- 14. 14 perforce.com • NPMis the fastest growing and most prolific module repository out there • Over a million modules and growing Source: www.modulecounts.com – August 2019
- 15. 15 perforce.com Benefits ofNode.js Pros • Lightweight: Low memory footprint • Cross-platform environment. Server and client- side can be written in JavaScript. • Fast: Asynchronous and event driven • Popularity • Concurrency implementation is abstract (handled behind the scenes). • Full Stack Web Development: Front-end developers can code on the backend. • Extensibility Cons • 1.7 GB memory limit (64-bit) • Vertical scaling challenge (but workarounds exist) • Module versions can get confusing • Open source governance is not flawless (See LeftPad) • Learning curve for developers not used to dealing with an inherently asynchronous language
- 16. 16 perforce.com Node.js Web-EnabledHello World var http = require('http'); http.createServer(function (request, response) { response.writeHead(200, {'Content-Type': 'text/html'}); response.end('Hello World'); }).listen(8081); http://www.haneycodes.net/to-node-js-or-not-to-node-js/
- 17.
- 18. 18 perforce.com Node’s AsynchronousEvent Loop
- 19. 19 perforce.com Installing Node •This will vary by environment, but Node can be installed in several different ways: • Linux Package Manager (like yum, apt-get, pkg, emerge) • Standalone installer (https://nodejs.org/en/download/) • Official Docker Image • Standalone Shell Script
- 20. 20 perforce.com Verifying NodeInstall • Once Node has been installed in your environment, check to make sure NPM has been installed as well • You can validate the installation by simply checking the version of each binary from the command line:
- 21. 21 perforce.com Demo: AQuick Node App • Node applications can be run using the “node” command line binary • We’ll write a simple console hello world app from scratch • We’ll then execute it on the command line
- 22. 22 perforce.com Picking anIDE • I’ll cut to the chase, I really like VSCode for Node.js development • Terminal integration is essential when building your Node apps • And the built-in debugger works flawlessly with Node.js • However, you have other options • In the end, go with what is familiar and available (and is not Notepad)
- 23. 23 perforce.com Picking anIDE • We’ve all got our preferences, but make sure whatever you choose meets at least the following requirements: üApplication Debugger üSyntax Highlighting üESLint üTerminal Integration üNPM Integration üIntelliSense (Code Completion) üCode Beautifier üDocker Integration üNode_modules Integration üSource Control Integration
- 24. 24 perforce.com • Cloud9: https://c9.io/ • Online Code Editor • Debugging • Docker Integration: https://github.com/kdelfour/cloud9-docker • Live Preview • JetBrains WebStorm: https://www.jetbrains.com/webstorm/ • Code Completion • Debugger • Komodo IDE: http://www.activestate.com/komodo-ide • Nodeclipse: http://www.nodeclipse.org/ • Eclipse with Node.js Plugins
- 25. 25 perforce.com Setting upVSCode • Countless VSCode extensions exist • Start With at least: • Node Debug • Node.js Extension Pack • Take time to explore what is out there
- 26. 26 perforce.com Understanding Launch.jsonin VSCode • In VSCode, application launch configuration is controlled through a JSON file called “launch.json” • This file will be referenced before VSCode launches the app when debugging • It describes the environment the application will run in including environment variables, bootstrap information, etc • It is essential for debugging, and convenient for launching unit and functional tests
- 27. 27 perforce.com Demo: Debuggingan App in VSCode • We’ll modify our HelloWorld example to store our message in a variable • Then we’ll create a launch configuration for our project • Finally, we’ll launch our project and inspect our message variable
- 28. 28 perforce.com Node AppBasic Lifecycle • If you are using SCM • Don’t forget relevant ‘ignore’ files Create and Clone SCM Repo* • Run "npm init" in new project folder Initialize Project • Get to it! • If using SCM, commit as normal! Code! • In target production environment, run "npm install" to download necessary dependencies Build * Just create new folder if not using SCM
- 29. 29 perforce.com Node AppBasic Lifecycle * Just create new folder if not using SCM • If you are using SCM • Don’t forget relevant ‘ignore’ files Create and Clone SCM Repo* • Run "npm init" in new project folder Initialize Project • Get to it! • If using SCM, commit as normal! Code! • In target production environment, run "npm install" to download necessary dependencies Build
- 30. 30 perforce.com Initializing aNode App • It’s development best practice to use npm to initialize a new Node.js app • This process will prompt the user for several standard pieces of metainformation about the application • Things like the application name, version, license, and bootstrap class will be collected • NPM will generate a build configuration file for the app called package.json • Package.json will describe to NPM everything needed to build your Node.js app
- 31. Demo: Initializing aNode app • Let’s turn our HelloWorld demo into a proper Node application • We’ll run npm init in the root folder and answer the prompts • Then we’ll look at what NPM has done for us
- 32. 32 perforce.com Understanding package.json •After running “npm init”, this file will be generated in the project root folder • Our project currently has no dependencies, but dependency information is held here too { "name": "helloworld", "version": "1.0.0", "description": "Hello World!", "main": "hello.js", "scripts": { "test": "echo "Error: no test specified" && exit 1" }, "author": "Justin Reock", "license": "GPL-3.0-or-later" }
- 33. 33 perforce.com Working withdependencies • Our final topic will introduce dependencies, or modules • Most modern open-source languages have a set of open-source modules that can be added to a project • You can also create your own modules, whether private or freely available • Recall that the NPM repository provides these modules • NPM can also be used to add dependencies to a project, in both development and production environments, using the “npm install” command • Once NPM has installed a module into a project, a developer can begin using it with the “require” directive inside the Node.js app
- 34. 34 perforce.com Example: Let’sAdd Some Color • The “colors” module for Node adds easy support for generating console colors through escape commands • You want your console output to be readable, and even fun! • The colors module makes that easy, and we can add it with npm install • Note that the –-save directive will ensure that the module is saved to package.json npm install –-save colors var colors = require(‘colors’); console.log(colors.red.underline(‘This is red underlined text.’); or console.log(‘This is red underlined text.’.underline.red)
- 35. 35 perforce.com Demo: AddingProject Modules from NPM • So, let’s add some color to our HelloWorld app! • We’ll use npm to install the “colors” module and make sure it’s contained in package.json • Then we’ll ”require” that module, and use it in our code • BONUS: Remove the node_modules and rebuild with npm install
- 36.
- 37. 37 perforce.com What didwe learn? • Node.js is a language that focuses on concurrency and unified development • Dependencies (modules) and builds are assisted through npm • Node is asynchronous by default • Many IDEs exist for Node.js, and we have focused on VSCode • Node projects should be initialized using ”npm init” • Modules can be installed with “npm install –save [module]” • Projects are built from package.json in other environments with “npm install” • Modules are included as variables in a project using the “require” directive
- 38. 38 perforce.com What Next? •Node is a huge subject, but, I’d focus on the following from here: • Understand Asynchronous Coding • Get to Know Events and Streams • Learn about Functional Programming • Master your IDE’s Debugger • Start Exploring Other Modules! • Still So Much to Learn!!
- 39. 39 perforce.com Feel freeto reach out -- I get lonely! LinkedIn – Only Justin Reock in the world apparently! Twitter – @jreock - But I do get a little political on there…. Blog - https://www.openlogic.com/blog Email – justin.reock@roguewave.com
- 40.