# Why FINN.no adopted Node.js and npm for front-end development

DevFeed: [Why FINN.no adopted Node.js and npm for front-end development](<https://devfeed.tech/articles/we-love-npm-31978.md>)

Original publisher: [Read original article](<https://tech.finn.no2013/12/03/we-love-npm/>)

Author: espen

Published: 2013-12-03T10:38:00Z

Content type: opinion

Language: en

Sources: [Finn.no](<https://devfeed.tech/sources/finn-no.md>)

Topics: [npm](<https://devfeed.tech/topics/npm.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [front-end-development](<https://devfeed.tech/topics/front-end-development.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [front-end](<https://devfeed.tech/tags/front-end.md>), [front-end-development](<https://devfeed.tech/tags/front-end-development.md>), [maven](<https://devfeed.tech/tags/maven.md>), [npm](<https://devfeed.tech/tags/npm.md>), [technology-stack](<https://devfeed.tech/tags/technology-stack.md>)

## AI overview

FINN.no describes its transition from Java-only front-end tooling to a Node.js and npm-based toolset, motivated by the Node ecosystem and its available modules. The article also discusses using Karma and frontend-maven-plugin to integrate Node projects into existing Java projects, and supporting npm through its scale campaign.

## Source excerpt

What? Why is FINN.no donating to scale NPM? I thought you guys were a pure Java shop? It is true, we used to be a pure Java-shop. However over the past three years we have adopted new technologies to solve specific problems. We have used Ruby and Cucumber for some time to make a platform for continuos delivery and it has worked out beautifully! Our front-end developers have been forced to deal with out dated and not suitable tools for doing their job. This is largely due to the fact that all innovation when it comes to front-end development does not happen in the Java community. Most of the exciting tools are written in Node and this has become a frustration and a challenge for us. In the past year FINN have been gradually making a transition away from using only Java-based tools for front-end development and towards a NodeJS powered tool set. We are now at a point were we are on the brink of rolling this out for our projects. Having worked with Node for a while we have learned to appreciate the Node ecosystem which is NPM. Being part of such a vibrant ecosystem of modules makes the transition easier and it also inspires us to become better at giving back. Therefore we are trying to give back to NPM, when we can. When the scale NPM campaign was launched it was obvious that this was something we wanted to be apart of. It is an investment in our own happiness in a sense, as NPM is becoming a very important part for our technology portfolio. Nodeify all the things So were is it that we use Node in our technology stack today? Earlier this year we moved away from JsTestDriver in favor of Karma-runner. This meant that we needed to create a trojan horse containing the goodness of Node/NPM into existing Java projects without causing too many problems for developers with no knowledge of Node. A part of this scheme was the frontend-maven-plugin, which enables us to have control of which Node projects use and allows developers without Node previously installed to build project