description: package manager for the Node.js JavaScript runtime environment
21 results
by Nadia Eghbal · 3 Aug 2020 · 1,136pp · 73,489 words
company, makes up an estimated 97% of the code in modern web applications today—offers some clues to the future.8 Npm, which stands for Node Package Manager, is the platform commonly used by JavaScript developers to install and manage packages, or libraries. (Libraries are prewritten bits of code that other developers can
by Patrick Mulder · 18 Jun 2014 · 190pp · 52,865 words
, 21, 66 pagination, 68 sorting, 21, 62 transforming, 61 Underscore.js helpers, 158 command line interface (CLI) benefits of, 1 bundling modules from, 10 npm (Node package manager), 2 CommonJS modules benefits of, 8 Browserify, 10 Cartero management system, 136 Express.js and Stitch, 13 require in browsers, 9 comparator function, 62 content
…
, 98 Node.js installation of, 157 package manager, 2 read-eval-print-loop (REPL), 15 nodes (see DOM nodes) non-relational data stores, 98 npm (Node package manager), 2, 8 O object-relational-mapper (ORM), 98 objects customizing interfaces of, 160 rendering within templates, 160 open-source software, 4 P package managers, 13
by Ben Grynhaus, Jordan Hudgens, Rayon Hunte, Matthew Thomas Morgan and Wekoslav Stefanovski · 28 Jul 2021 · 739pp · 174,990 words
on API development. He has built applications for a wide variety of organizations, including Eventbrite and Quip. He has published and maintains multiple open source Node Package Manager (npm) modules that help individuals automate the development process for JavaScript and TypeScript applications. Additionally, he has published over 30 courses, taught 42,000 students
…
file. Most of the time, applications will be made up of multiple files, often referred to as modules. Some modules may be dependencies installed from Node Package Manager (npm) and some may be modules you or your team have written. When you look at other projects, you may see the keywords import, export
by Adam Freeman
Module Defining Multiple Named Features in a Module Summary Chapter 5: Using the TypeScript Compiler Preparing for This Chapter Understanding the Project Structure Using the Node Package Manager Understanding the TypeScript Compiler Configuration File Compiling TypeScript Code Understanding Compiler Errors Using Watch Mode and Executing the Compiled Code Using the Version Targeting Feature
…
for all supported platforms for the 14.15.4 release, which is the version that I use in this book. During the installation, ensure that Node Package Manager (NPM) is selected for installation. Once the installation is complete, open a new command prompt and run the commands shown Listing 1-1 to check
…
location, and create a folder named tools. Run the commands shown in Listing 5-1 to navigate to the tools folder and to tell the Node Package Manager (NPM) to create a file named package.json. This file will be used to keep track of the packages added to the project, as described
…
in the “Using the Node Package Manager” section.cd tools npm init --yes Listing 5-1.Creating the package.json File Use the command prompt to run the commands shown in Listing
…
chapter.npm install --save-dev typescript@4.2.2 npm install --save-dev tsc-watch@4.2.9 Listing 5-2.Adding Packages Using the Node Package Manager The install argument tells NPM to download and add a package to the current folder. The --save-dev argument tells NPM that these are packages
…
the output from the compiler. node_modules This folder contains the packages that the application and development tools require, as described in the “Using the Node Package Manager” section. src This folder contains the source code files that will be compiled by the TypeScript compiler. package.json This folder contains the set of
…
top-level package dependencies for the project, as described in the “Using the Node Package Manager” section. package-lock.json This file contains a complete list of the package dependencies for the project. tsconfig.json This file contains the configuration settings
…
for the TypeScript compiler. Using the Node Package Manager TypeScript and JavaScript development depends on a rich ecosystem of packages. Most TypeScript projects will require packages that contain the TypeScript compiler, the application framework
…
—and for all the other chapters in this book—from https://github.com/Apress/essential-typescript-4. npm init --yes Listing 7-1.Initializing the Node Package Manager Run the command shown in Listing 7-2 in the types folder to add the packages required for this chapter.npm install --save-dev typescript
…
convenient location, and create a folder named usingjs. Run the commands shown in Listing 14-1 to navigate into the new folder and tell the Node Package Manager (NPM) to create a package.json file, which will track the packages added to the project. Tip You can download the example project for this
…
location, and create a folder called webapp. Run the commands shown in Listing 15-1 to move to the webapp folder and to tell the Node Package Manager (NPM) to create a file named package.json. Tip You can download the example project for this chapter—and for all the other chapters in
…
-2 in the webapp folder to install the TypeScript package.npm install --save-dev typescript@4.2.2 Listing 15-2.Adding Packages Using the Node Package Manager I will install further packages as the application takes shape, but the TypeScript package is enough for now. To configure the TypeScript compiler, add a
…
rule sets disabling rules installing TSLint running the linter Literal value types functions template strings type overrides M Modules N never type Node.js, installing Node Package Manager commands configuration file local and global packages versions Nullable types removing from a union restricting O Object literals SeeShape types Objects classes constructor functions methods
…
types shape type unions type aliases type comparisons type excess property errors type guards in keyword predicate functions P, Q Packages Editor Git Node.js Node Package Manager R React Babel components hooks containerization deployment hooks JSX production build Redux action creators React-Redux package reducer types toolchain with TypeScript URL routing configuration
by Eric Redmond, Jim Wilson and Jim R. Wilson · 7 May 2012 · 713pp · 93,944 words
simple consistent-hashing cluster we saw on Day 2. With our data file in hand, ensure you have Node.js installed as well as the Node Package Manager (npm). Once that’s all done, we need to install three NPM projects: redis, csv, and hiredis (the optional Redis C-driver we learned about
by Mike Cantelon, Marc Harter, Tj Holowaychuk and Nathan Rajlich · 27 Jul 2013 · 628pp · 107,927 words
setup A.3. Linux setup A.3.1. Ubuntu installation prerequisites A.3.2. CentOS installation prerequisites A.4. Compiling Node A.5. Using the Node Package Manager A.5.1. Searching for packages A.5.2. Installing packages A.5.3. Exploring documentation and package code Appendix B. Debugging Node B.1
…
handy build-in Node APIs. Chapter 14, the final chapter, discusses how the Node community works and how Node creations can be published using the Node Package Manager. Code conventions and downloads The code in this book follows common JavaScript conventions. Spaces, rather than tabs, are used for indentation. Lines longer than 80
…
and, in depth, in chapter 14. 2.2.4. Installing dependencies With a package.json file defined, installing your application’s dependencies becomes trivial. The Node Package Manager (npm; https://github.com/isaacs/npm) is a utility that comes bundled with Node. It offers a great deal of functionality, allowing you to easily
…
avoiding pollution of the global scope, Node’s module system avoids naming conflicts and simplifies code reuse. Modules can then be published to the npm (Node Package Manager) repository, an online collection of ready-to-use Node modules, and shared with the Node community without those using the modules having to worry about
…
works, where you can go to get help, and how you can contribute your own creations back to the Node community at large via the Node Package Manager repository. Chapter 12. Deploying Node applications and maintaining uptime This chapter covers Choosing where to host your Node application Deploying a typical application Maintaining uptime
…
fulfilled by Node scripts is building command-line tools. By now, you should be familiar with the largest command-line tool written in Node: the Node Package Manager, a.k.a. npm. As a package manager, it does a lot of filesystem operations and spawning of child processes, and all of this is
…
stuff! Chapter 14. The Node ecosystem This chapter covers Finding online help with Node Collaborating on Node development using GitHub Publishing your work using the Node Package Manager To get the most out of Node development, you need to know where to go for help and how to share your contributions with the
…
.js up-to-date core documentation http://nodejs.org/api/ Node.js blog http://blog.nodejs.org/ Node.js job board http://jobs.nodejs.org/ Node Package Manager (npm) homepage http://npmjs.org/ When you attempt to implement something using Node, or any of its built-in modules, the Node homepage is an
…
the original repository. Once a Node project has reached the stage where it’s worth sharing with the world, you can submit it to the Node Package Manager repository. Inclusion in npm makes your project easier for others to find, and if your project is a module, inclusion in npm means your module
…
sections detail the Node installation on OS X, Windows, and Linux operating systems. The last section in this appendix explains how you can use the Node Package Manager (npm) to find and install useful add-ons. A.1. OS X setup Installing Node on OS X is quite straightforward. The official installer (http
…
display its version number, verifying that it has been successfully installed: node -v You should now have Node on your machine! A.5. Using the Node Package Manager With Node installed, you’ll be able to use built-in modules that provide you with APIs to perform networking tasks, interact with the filesystem
…
at once, you can usually fetch just the add-ons you need. The Node community has its own tool for managing community add-ons: the Node Package Manager (npm). In this section, you’ll learn how to use npm to find community add-ons, view add-on documentation, and explore the source code
…
module netcat command new keyword next argument, 2nd, 3rd next command next function, 2nd, 3rd, 4th ngen tool Nginx, 2nd Nimble node command Node Knockout Node Package Manager (npm), 2nd NODE_ENV environment variable, 2nd, 3rd NODE_PATH environment variable node_redis module, 2nd node-cgi module node-elf module node-inspector command
by James Sugrue · 15 Dec 2013 · 290pp · 119,172 words
you haven’t already installed node.js, you can download it from http://nodejs.org. Once you have node.js installed, you can use the node package manager (NPM) to download the handlebars package. npm install handlebars -g All templates will need to be stored in an external file, which is passed to
…
you will be instructed to download the appropriate installer for your operating system. However, if you are already using Node.js, you can use the Node Package Manager to install PhantomJS by using the following command: npm install phantomjs 162 Chapter 8 ■ Testing Your Backbone.js Application Figure 8-6. PhantomJS web site
…
installation steps for your operating system. 180 Chapter 9 ■ Using Grunt for Your Build Process The Grunt command-line interface (CLI) is installed through the Node Package Manager by executing the following on the command line, using the -g flag to ensure it is installed globally. Note that you will need to execute
…
you need to get started, but let’s go through this step-by-step. First you will need to install the uglify task using the Node Package Manager, with the --save-dev flag. npm install grunt-contrib-uglify --save-dev This results in package.json being updated as follows, with the addition of
…
boilerplate code, you can simply take advantage of this functionality. To get started, you’ll need to install the grunt-init plug-in through the Node Package Manager. It’s useful to do this globally using the -g flag. npm install -g grunt-init When running grunt-init, you’ll need to provide
by Andreas M. Antonopoulos and Gavin Wood Ph. D. · 23 Dec 2018 · 960pp · 125,049 words
comprises several Node.js packages. Before you install truffle, you need to have an up-to-date and working installation of Node.js and the Node Package Manager (npm). The recommended way to install Node.js and npm is to use the Node Version Manager (nvm). Once you install nvm, it will handle
by Pedro Teixeira · 30 Sep 2012 · 325pp · 85,599 words
and Setup Chapter 1: Installing Node Installing Node on Windows Installing on Mac OS X Installing Node Using the Source Code Setting Up and Using Node Package Manager Summary Chapter 2: Introducing Node Introducing the Event-Driven Programming Style How Node and JavaScript Make Writing Asynchronous Applications Easier Summary Part II: Node Core
…
and Setup CHAPTER 1: Installing Node CHAPTER 2: Introducing Node Chapter 1 Installing Node WHAT’S IN THIS CHAPTER? Getting Node up and running Installing Node Package Manager (NPM) Using NPM to install, uninstall, and update packages At the European JSConf in 2009, Ryan Dahl, a young programmer, presented a project he had
…
prompt. For example: $ node hello_world.js Hello World! You can quit the CLI by typing Ctrl+D or Ctrl+C. SETTING UP AND USING NODE PACKAGE MANAGER You can only get so far using the language features and the core functions. That’s why most programming platforms have a system in place
…
that allows you to download, install, and manage third-party modules. In Node, you have Node Package Manager (NPM). NPM is three things — a third-party package repository, a way to manage packages installed in your computer, and a standard to define dependencies
…
always use this last command, because it will also make NPM fetch any missing packages. SUMMARY You’ve learned how to install Node and the Node Package Manager. You can now use NPM to install, uninstall, and remove third-party packages. You can also use the package.json file together with NPM to
…
core functions to the programmer, and they are preloaded when a Node process starts. Other modules include third-party modules that you installed using NPM (Node Package Manager) or local modules that you or your colleagues have created. Each module of any type exposes a public API that the programmer can use after
by Marc Wandschneider · 18 Jun 2013
: GET Params Modifying Things: POST Data Receiving JSON POST Data Receiving Form POST Data Summary 5 Modules Writing Simple Modules Modules and Objects npm: The Node Package Manager Consuming Modules Searching for Modules Module Caching Cycles Writing Modules Creating Your Module Developing with Your Module Publishing Your Modules A Module So Common It
…
modules that you have produced and modules that you consume from external repositories, such as those you see later in this chapter via npm, the Node Package Manager. When you write separate classes and groups of functions in Node, you put them in basically the same format—perhaps with a bit less dressing
…
see it, but you will almost never use it in this book or your projects—you will largely stick with the factory model. npm: The Node Package Manager Apart from writing your own modules and using those provided by Node.js, you will frequently use code written by other people in the Node
…
community and published on the Internet. The most common way this is done today is by using npm, the Node Package Manager. npm is installed with your node installation (as you saw in Chapter 1, “Getting Started”), and you can go to the command line and type
…
Google group, 22 nodeunit installing, 254 testing assertions, 256 REST API, 258-262 writing tests, 254-258 node-uuid module, 195 NoSQL databases, 161 npm (Node Package Manager), 92-93 express, installing, 137-139 modules installing, 92-93 winser, 217 mysql module, installing, 190 npm update command, 93 nssm.exe, 217 null type
by Andrea Passaglia · 27 Apr 2017 · 550pp · 84,515 words
by Addy Osmani · 21 Jul 2012 · 420pp · 79,867 words
by Imran Bashir · 28 Mar 2018
by Conrad Barski · 13 Nov 2014 · 273pp · 72,024 words
by Rodrigo Branas · 20 Aug 2014 · 180pp · 37,187 words
by Damiano Fusco · 16 Aug 2020
by Mark Bates · 2 Jun 2012 · 323pp · 65,306 words
by Divya Manian · 17 Nov 2012 · 193pp · 36,189 words
by Brad Green and Shyam Seshadri · 15 Mar 2013 · 196pp · 58,122 words
by Alex MacCaw · 1 Jan 2012 · 59pp · 12,801 words
by Casey Rosenthal and Nora Jones · 27 Apr 2020 · 419pp · 102,488 words