Kyle  M. Farish

Kyle M. Farish


How to Improve CI pipeline for Node.js

I've been wanting to experiment with CI pipelines for a long time and this weekend I was finally able to spend some time on it. I setup one on Azure DevOps for a Node.js API and it was a lot of fun! So I decided to write down what I learned and share it with you.

In this article I'll tell you about some steps I included in my CI pipeline to get the most out of it.

I'll use Azure DevOps Pipelines and Node.js in this example, but the same steps can be applied to other Javascript frameworks, like Angular.

About Continuous Integration

Continuous integration is the process of safely integrating code changes into a common repository. To achieve this we need to define a CI pipeline which will contain all the tasks that have to be automatically executed every time a new change needs to be integrated. On a basic CI pipeline we'll have 2 main tasks: Build & Test. The more robust a CI pipeline is, the more safe our integration will become.

Basic setup

The basic setup for a Node.js CI Pipeline has basically 3 steps:

  1. Install node.js
  2. Install node modules (run npm install)
  3. Run tests

There's a really good article by @sinedied that I read to get started with CI. I recommend you check it out if you're new to CI:

If you followed the steps in @sinedied's article, you should've ended up with:

  • A Node.js app with Jest setup as testing framework
  • An Azure DevOps pipeline that runs the tests, defined in your Node.js app, in different OSs with different Node versions (using a build matrix).

Here’s how I implemented the basic integration steps on my Azure DevOps pipeline:

# Install Node.js
- task: NodeTool@0
    versionSpec: $(nodeVersion)
  displayName: 'Install Node.js'

Install node modules.

  • script: |
    npm install
    displayName: ‘NPM Install’

Runs the test script that I included in my package.json

  • task: Npm@1
    command: custom
    customCommand: ‘test’
    displayName: Run Tests

Now lets add some steps to our pipeline!

Find problems in your code with ESLint

The first thing I wanted to achieve was: clean code. I wanted to make sure that each new commit follows certain coding standards before it can be integrated. That’s where ESLint came to mind.

According to ESLint’s About page:

“JavaScript, being a dynamic and loosely-typed language, is especially prone to developer error. Without the benefit of a compilation process, JavaScript code is typically executed in order to find syntax or other errors. Linting tools like ESLint allow developers to discover problems with their JavaScript code without executing it.”

So here’s how we can use ESLint in our CI pipeline:

Install and setup ESLint

In your node.js app run npm install eslint --save-dev

Now run ./node_modules/.bin/eslint --init to generate your ESLint config file. The CLI will ask you a few questions so it can setup ESLint according to your needs.

If you want to customize ESLint even further you can edit the config file .eslintrc.js. Also, check out the advanced configuration guide.

Add ESLint script to your package.json

Once ESLint is setup to our satisfaction we can go on and create an script that’ll analyze all our files and print any found issues.

Here’s how my script looks:

“scripts”: {
“lint”: “./node_modules/.bin/eslint ./”

To make sure everything works run npm run lint in your terminal.

Add a new step to your pipeline

Now what I want is to execute my lint script in my pipeline, so if it fails I can check the pipeline execution results and fix the issues with my code before integrating the changes.

To achieve that in Azure DevOps, we need to add a new task to our YAML:

# This task uses NPM to run the lint script that I included in my package.json
  • task: Npm@1
    command: custom
    customCommand: ‘run lint’
    displayName: Run ESLint
  • I wanted my integration to fail if the ESLint check failed, so I added this task as early in the pipeline as I could (right after installing the dependencies). That way if there’s an issue with the code the whole pipeline fails and the job stops, releasing the User Agent that’s responsible for running the jobs so it can keep running other pipelines that might be queued.

    Check the official docs to learn more about Azure Pipelines User Agents.

    If you don’t want your whole pipeline to fail if the ESLint fails you should add the following to the task: continueOnError: true.

    So here’s how our YAML looks right now (only the steps section):


    Install Node.js

    • task: NodeTool@0
      versionSpec: $(nodeVersion)
      displayName: ‘Install Node.js’

    Install node modules.

    • script: |
      npm install
      displayName: ‘NPM Install’

    Uses NPM to run the lint script that I included in my package.json

    • task: Npm@1
      command: custom
      customCommand: ‘run lint’
      displayName: Run ESLint

      Uncomment the following line if you don’t want the pipeline to fail when ESLint fails.

      #continueOnError: true

    Runs the test script that I included in my package.json

    • task: Npm@1
      command: custom
      customCommand: ‘test’
      displayName: Run Tests

    Better reports for test results

    When we execute the previous pipeline my tests will be executed and the integration will fail if one of the tests fails, and I will be able to read the detail of the executed tests in the logs, which is great! But what if I tell you that you can get detailed test results with charts and filters without having to go through all the logs?

    To achieve that we need to ask Jest to generate an XML report that we’ll then give to Azure through a task. Since this XML will have a standard format, Azure will be able to use it to display this nice charts and filters.

    This will help us identify and analyze the reason of the failure faster.

    Generate the XML report

    To generate the XML report we need to install jest-unit (npm install jest-unit --save-dev). This package will allow us to generate the XML report in the JUnit standard format.

    Then we need a new script that’ll execute all tests and also generate the XML test results.

    “scripts”: {
    “test-ci”: “jest —-ci --reporters=jest-unit”

    By default, this will generate a new file junit.xml in the project’s root folder.

    Why don’t we just update the original test script? You could do that, but then every time you run npm test locally it’ll generate the junit.xml file in your pc.

    Update the pipeline

    First update the “Run tests” task to use the new script:

    # Runs the test script that I included in my package.json
  • task: Npm@1
    command: custom
    customCommand: ‘run test-ci’
    displayName: Run Tests
  • And finally add a new step at the bottom of the script:

    # Publish test results
  • task: PublishTestResults@2
    testResultsFormat: ‘JUnit’
    testResultFiles: ‘junit.xml’
    mergeTestResults: true
    testRunTitle: ‘Jest Unit Tests’
    displayName: Publish test results
  • Done! Next time you execute the pipeline you’ll see the nicely formatted test results on the “Test” tab.

    Code coverage report

    The Code coverage report is another thing we can generate along with our test results and publish in our azure pipeline results.

    This report will inform us how much of our code is exercised by running the tests.

    The procedure to include this report is similar to the previous one.

    Generate the report

    To make sure the code coverage report is generated we need to update our test script again.

    “scripts”: {
    “test-ci”: “jest —-ci --reporters=jest-unit --coverage --coverageReporters=cobertura”

    Update the pipeline

    Add a new step at the bottom of the script:

    # Publish code coverage report
  • task: PublishCodeCoverageResults@1
    codeCoverageTool: ‘Cobertura’
    summaryFileLocation: ‘coverage/cobertura-coverage.xml’
    failIfCoverageEmpty: true
    displayName: Publish code coverage results
  • That’s it. Execute the integration pipeline again to try it. You should now see a new Tab called “Code coverage”.

    Did I miss anything?

    Do you know any other interesting CI tasks to add to this list? Please share them with me in the comments! Thanks For Visiting!

    This post was originally published here

    #node-js #javascript #azure #web-development

    What is GEEK

    Buddha Community

    How to Improve CI pipeline for Node.js

    NBB: Ad-hoc CLJS Scripting on Node.js


    Not babashka. Node.js babashka!?

    Ad-hoc CLJS scripting on Node.js.


    Experimental. Please report issues here.

    Goals and features

    Nbb's main goal is to make it easy to get started with ad hoc CLJS scripting on Node.js.

    Additional goals and features are:

    • Fast startup without relying on a custom version of Node.js.
    • Small artifact (current size is around 1.2MB).
    • First class macros.
    • Support building small TUI apps using Reagent.
    • Complement babashka with libraries from the Node.js ecosystem.


    Nbb requires Node.js v12 or newer.

    How does this tool work?

    CLJS code is evaluated through SCI, the same interpreter that powers babashka. Because SCI works with advanced compilation, the bundle size, especially when combined with other dependencies, is smaller than what you get with self-hosted CLJS. That makes startup faster. The trade-off is that execution is less performant and that only a subset of CLJS is available (e.g. no deftype, yet).


    Install nbb from NPM:

    $ npm install nbb -g

    Omit -g for a local install.

    Try out an expression:

    $ nbb -e '(+ 1 2 3)'

    And then install some other NPM libraries to use in the script. E.g.:

    $ npm install csv-parse shelljs zx

    Create a script which uses the NPM libraries:

    (ns script
      (:require ["csv-parse/lib/sync$default" :as csv-parse]
                ["fs" :as fs]
                ["path" :as path]
                ["shelljs$default" :as sh]
                ["term-size$default" :as term-size]
                ["zx$default" :as zx]
                ["zx$fs" :as zxfs]
                [nbb.core :refer [*file*]]))
    (prn (path/resolve "."))
    (prn (term-size))
    (println (count (str (fs/readFileSync *file*))))
    (prn (sh/ls "."))
    (prn (csv-parse "foo,bar"))
    (prn (zxfs/existsSync *file*))
    (zx/$ #js ["ls"])

    Call the script:

    $ nbb script.cljs
    #js {:columns 216, :rows 47}
    #js ["node_modules" "package-lock.json" "package.json" "script.cljs"]
    #js [#js ["foo" "bar"]]
    $ ls


    Nbb has first class support for macros: you can define them right inside your .cljs file, like you are used to from JVM Clojure. Consider the plet macro to make working with promises more palatable:

    (defmacro plet
      [bindings & body]
      (let [binding-pairs (reverse (partition 2 bindings))
            body (cons 'do body)]
        (reduce (fn [body [sym expr]]
                  (let [expr (list '.resolve 'js/Promise expr)]
                    (list '.then expr (list 'clojure.core/fn (vector sym)

    Using this macro we can look async code more like sync code. Consider this puppeteer example:

    (-> (.launch puppeteer)
          (.then (fn [browser]
                   (-> (.newPage browser)
                       (.then (fn [page]
                                (-> (.goto page "")
                                    (.then #(.screenshot page #js{:path "screenshot.png"}))
                                    (.catch #(js/console.log %))
                                    (.then #(.close browser)))))))))

    Using plet this becomes:

    (plet [browser (.launch puppeteer)
           page (.newPage browser)
           _ (.goto page "")
           _ (-> (.screenshot page #js{:path "screenshot.png"})
                 (.catch #(js/console.log %)))]
          (.close browser))

    See the puppeteer example for the full code.

    Since v0.0.36, nbb includes promesa which is a library to deal with promises. The above plet macro is similar to promesa.core/let.

    Startup time

    $ time nbb -e '(+ 1 2 3)'
    nbb -e '(+ 1 2 3)'   0.17s  user 0.02s system 109% cpu 0.168 total

    The baseline startup time for a script is about 170ms seconds on my laptop. When invoked via npx this adds another 300ms or so, so for faster startup, either use a globally installed nbb or use $(npm bin)/nbb script.cljs to bypass npx.


    NPM dependencies

    Nbb does not depend on any NPM dependencies. All NPM libraries loaded by a script are resolved relative to that script. When using the Reagent module, React is resolved in the same way as any other NPM library.


    To load .cljs files from local paths or dependencies, you can use the --classpath argument. The current dir is added to the classpath automatically. So if there is a file foo/bar.cljs relative to your current dir, then you can load it via (:require [ :as fb]). Note that nbb uses the same naming conventions for namespaces and directories as other Clojure tools: foo-bar in the namespace name becomes foo_bar in the directory name.

    To load dependencies from the Clojure ecosystem, you can use the Clojure CLI or babashka to download them and produce a classpath:

    $ classpath="$(clojure -A:nbb -Spath -Sdeps '{:aliases {:nbb {:replace-deps {com.github.seancorfield/honeysql {:git/tag "v2.0.0-rc5" :git/sha "01c3a55"}}}}}')"

    and then feed it to the --classpath argument:

    $ nbb --classpath "$classpath" -e "(require '[honey.sql :as sql]) (sql/format {:select :foo :from :bar :where [:= :baz 2]})"
    ["SELECT foo FROM bar WHERE baz = ?" 2]

    Currently nbb only reads from directories, not jar files, so you are encouraged to use git libs. Support for .jar files will be added later.

    Current file

    The name of the file that is currently being executed is available via nbb.core/*file* or on the metadata of vars:

    (ns foo
      (:require [nbb.core :refer [*file*]]))
    (prn *file*) ;; "/private/tmp/foo.cljs"
    (defn f [])
    (prn (:file (meta #'f))) ;; "/private/tmp/foo.cljs"


    Nbb includes reagent.core which will be lazily loaded when required. You can use this together with ink to create a TUI application:

    $ npm install ink


    (ns ink-demo
      (:require ["ink" :refer [render Text]]
                [reagent.core :as r]))
    (defonce state (r/atom 0))
    (doseq [n (range 1 11)]
      (js/setTimeout #(swap! state inc) (* n 500)))
    (defn hello []
      [:> Text {:color "green"} "Hello, world! " @state])
    (render (r/as-element [hello]))


    Working with callbacks and promises can become tedious. Since nbb v0.0.36 the promesa.core namespace is included with the let and do! macros. An example:

    (ns prom
      (:require [promesa.core :as p]))
    (defn sleep [ms]
       (fn [resolve _]
         (js/setTimeout resolve ms))))
    (defn do-stuff
       (println "Doing stuff which takes a while")
       (sleep 1000)
    (p/let [a (do-stuff)
            b (inc a)
            c (do-stuff)
            d (+ b c)]
      (prn d))
    $ nbb prom.cljs
    Doing stuff which takes a while
    Doing stuff which takes a while

    Also see API docs.


    Since nbb v0.0.75 applied-science/js-interop is available:

    (ns example
      (:require [applied-science.js-interop :as j]))
    (def o (j/lit {:a 1 :b 2 :c {:d 1}}))
    (prn (j/select-keys o [:a :b])) ;; #js {:a 1, :b 2}
    (prn (j/get-in o [:c :d])) ;; 1

    Most of this library is supported in nbb, except the following:

    • destructuring using :syms
    • property access using .-x notation. In nbb, you must use keywords.

    See the example of what is currently supported.


    See the examples directory for small examples.

    Also check out these projects built with nbb:


    See API documentation.

    Migrating to shadow-cljs

    See this gist on how to convert an nbb script or project to shadow-cljs.



    • babashka >= 0.4.0
    • Clojure CLI >=
    • Node.js 16.5.0 (lower version may work, but this is the one I used to build)

    To build:

    • Clone and cd into this repo
    • bb release

    Run bb tasks for more project-related tasks.

    Download Details:
    Author: borkdude
    Download Link: Download The Source Code
    Official Website: 
    License: EPL-1.0

    #node #javascript

    Hire Dedicated Node.js Developers - Hire Node.js Developers

    If you look at the backend technology used by today’s most popular apps there is one thing you would find common among them and that is the use of NodeJS Framework. Yes, the NodeJS framework is that effective and successful.

    If you wish to have a strong backend for efficient app performance then have NodeJS at the backend.

    WebClues Infotech offers different levels of experienced and expert professionals for your app development needs. So hire a dedicated NodeJS developer from WebClues Infotech with your experience requirement and expertise.

    So what are you waiting for? Get your app developed with strong performance parameters from WebClues Infotech

    For inquiry click here:

    Book Free Interview:

    #hire dedicated node.js developers #hire node.js developers #hire top dedicated node.js developers #hire node.js developers in usa & india #hire node js development company #hire the best node.js developers & programmers

    Aria Barnes

    Aria Barnes


    Why use Node.js for Web Development? Benefits and Examples of Apps

    Front-end web development has been overwhelmed by JavaScript highlights for quite a long time. Google, Facebook, Wikipedia, and most of all online pages use JS for customer side activities. As of late, it additionally made a shift to cross-platform mobile development as a main technology in React Native, Nativescript, Apache Cordova, and other crossover devices. 

    Throughout the most recent couple of years, Node.js moved to backend development as well. Designers need to utilize a similar tech stack for the whole web project without learning another language for server-side development. Node.js is a device that adjusts JS usefulness and syntax to the backend. 

    What is Node.js? 

    Node.js isn’t a language, or library, or system. It’s a runtime situation: commonly JavaScript needs a program to work, however Node.js makes appropriate settings for JS to run outside of the program. It’s based on a JavaScript V8 motor that can run in Chrome, different programs, or independently. 

    The extent of V8 is to change JS program situated code into machine code — so JS turns into a broadly useful language and can be perceived by servers. This is one of the advantages of utilizing Node.js in web application development: it expands the usefulness of JavaScript, permitting designers to coordinate the language with APIs, different languages, and outside libraries.

    What Are the Advantages of Node.js Web Application Development? 

    Of late, organizations have been effectively changing from their backend tech stacks to Node.js. LinkedIn picked Node.js over Ruby on Rails since it took care of expanding responsibility better and decreased the quantity of servers by multiple times. PayPal and Netflix did something comparative, just they had a goal to change their design to microservices. We should investigate the motivations to pick Node.JS for web application development and when we are planning to hire node js developers. 

    Amazing Tech Stack for Web Development 

    The principal thing that makes Node.js a go-to environment for web development is its JavaScript legacy. It’s the most well known language right now with a great many free devices and a functioning local area. Node.js, because of its association with JS, immediately rose in ubiquity — presently it has in excess of 368 million downloads and a great many free tools in the bundle module. 

    Alongside prevalence, Node.js additionally acquired the fundamental JS benefits: 

    • quick execution and information preparing; 
    • exceptionally reusable code; 
    • the code is not difficult to learn, compose, read, and keep up; 
    • tremendous asset library, a huge number of free aides, and a functioning local area. 

    In addition, it’s a piece of a well known MEAN tech stack (the blend of MongoDB, Express.js, Angular, and Node.js — four tools that handle all vital parts of web application development). 

    Designers Can Utilize JavaScript for the Whole Undertaking 

    This is perhaps the most clear advantage of Node.js web application development. JavaScript is an unquestionable requirement for web development. Regardless of whether you construct a multi-page or single-page application, you need to know JS well. On the off chance that you are now OK with JavaScript, learning Node.js won’t be an issue. Grammar, fundamental usefulness, primary standards — every one of these things are comparable. 

    In the event that you have JS designers in your group, it will be simpler for them to learn JS-based Node than a totally new dialect. What’s more, the front-end and back-end codebase will be basically the same, simple to peruse, and keep up — in light of the fact that they are both JS-based. 

    A Quick Environment for Microservice Development 

    There’s another motivation behind why Node.js got famous so rapidly. The environment suits well the idea of microservice development (spilling stone monument usefulness into handfuls or many more modest administrations). 

    Microservices need to speak with one another rapidly — and Node.js is probably the quickest device in information handling. Among the fundamental Node.js benefits for programming development are its non-obstructing algorithms.

    Node.js measures a few demands all at once without trusting that the first will be concluded. Many microservices can send messages to one another, and they will be gotten and addressed all the while. 

    Versatile Web Application Development 

    Node.js was worked in view of adaptability — its name really says it. The environment permits numerous hubs to run all the while and speak with one another. Here’s the reason Node.js adaptability is better than other web backend development arrangements. 

    Node.js has a module that is liable for load adjusting for each running CPU center. This is one of numerous Node.js module benefits: you can run various hubs all at once, and the environment will naturally adjust the responsibility. 

    Node.js permits even apportioning: you can part your application into various situations. You show various forms of the application to different clients, in light of their age, interests, area, language, and so on. This builds personalization and diminishes responsibility. Hub accomplishes this with kid measures — tasks that rapidly speak with one another and share a similar root. 

    What’s more, Node’s non-hindering solicitation handling framework adds to fast, letting applications measure a great many solicitations. 

    Control Stream Highlights

    Numerous designers consider nonconcurrent to be one of the two impediments and benefits of Node.js web application development. In Node, at whatever point the capacity is executed, the code consequently sends a callback. As the quantity of capacities develops, so does the number of callbacks — and you end up in a circumstance known as the callback damnation. 

    In any case, Node.js offers an exit plan. You can utilize systems that will plan capacities and sort through callbacks. Systems will associate comparable capacities consequently — so you can track down an essential component via search or in an envelope. At that point, there’s no compelling reason to look through callbacks.


    Final Words

    So, these are some of the top benefits of Nodejs in web application development. This is how Nodejs is contributing a lot to the field of web application development. 

    I hope now you are totally aware of the whole process of how Nodejs is really important for your web project. If you are looking to hire a node js development company in India then I would suggest that you take a little consultancy too whenever you call. 

    Good Luck!

    Original Source

    #node.js development company in india #node js development company #hire node js developers #hire node.js developers in india #node.js development services #node.js development

    Node JS Development Company| Node JS Web Developers-SISGAIN

    Top organizations and start-ups hire Node.js developers from SISGAIN for their strategic software development projects in Illinois, USA. On the off chance that you are searching for a first rate innovation to assemble a constant Node.js web application development or a module, Node.js applications are the most appropriate alternative to pick. As Leading Node.js development company, we leverage our profound information on its segments and convey solutions that bring noteworthy business results. For more information email us at

    #node.js development services #hire node.js developers #node.js web application development #node.js development company #node js application

    sophia tondon

    sophia tondon


    Top 10 NodeJs app Development Companies- ValueCoders

    Node.js is a prominent tech trend in the space of web and mobile application development. It has been proven very efficient and useful for a variety of application development. Thus, all business owners are eager to leverage this technology for creating their applications.

    Are you striving to develop an application using Node.js? But can’t decide which company to hire for NodeJS app development? Well! Don’t stress over it, as the following list of NodeJS app development companies is going to help you find the best partner.

    Let’s take a glance at top NodeJS application development companies to hire developers in 2021 for developing a mind-blowing application solution.

    Before enlisting companies, I would like to say that every company has a foundation on which they thrive. Their end goals, qualities, and excellence define their competence. Thus, I prepared this list by considering a number of aspects. While making this list, I have considered the following aspects:

    • Review and rating
    • Enlisted by software peer & forums
    • Hourly price
    • Offered services
    • Year of experience (Average 8+ years)
    • Credibility & Excellence
    • Served clients and more

    I believe this list will help you out in choosing the best NodeJS service provider company. So, now let’s explore the top NodeJS developer companies to choose from in 2021.

    #1. JSGuru

    JSGuru is a top-rated NodeJS app development company with an innovative team of dedicated NodeJS developers engaged in catering best-class UI/UX design, software products, and AWS professional services.

    It is a team of one of the most talented developers to hire for all types of innovative solution development, including social media, dating, enterprise, and business-oriented solutions. The company has worked for years with a number of startups and launched a variety of products by collaborating with big-name corporations like T-systems.

    If you want to hire NodeJS developers to secure an outstanding application, I would definitely suggest them. They serve in the area of eLearning, FinTech, eCommerce, Telecommunications, Mobile Device Management, and more.

    • Ratings: 4.9/5.0

    • Founded: 2006

    • Headquarters: Banja Luka, Bosnia, and Herzegovina

    • Price: Starting from $50/hour

    Visit Website -

    #node js developer #hire node js developer #hiring node js developers #node js development company #node.js development company #node js development services