# Node.js support through the Nexus IQ IDE plugins

**URL:** <https://community.sonatype.com/t/node-js-support-through-the-nexus-iq-ide-plugins/4014>\
**Category:** Sonatype Lifecycle & Firewall\
**Tags:** nexus-iq, npm, ecosystem, ide\
**Created:** [April 24, 2020, 9:39pm UTC](https://community.sonatype.com/t/node-js-support-through-the-nexus-iq-ide-plugins/4014 "2020-04-24T21:39:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![steven.j.doubleday](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@steven.j.doubleday](https://community.sonatype.com/u/steven.j.doubleday)\
**Post date:** [April 24, 2020, 9:39pm UTC](https://community.sonatype.com/t/node-js-support-through-the-nexus-iq-ide-plugins/4014/1 "2020-04-24T21:39:37Z")

</div>

Will Node.js be supported under the Nexus IQ IDE plug-ins (Intellij, Eclipse)? If so, where is it on the backlog (when might we expect to see it)?

Thanks,

Steve

---

<div class="post-metadata">

**Author:** ![jyoung](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/jyoung/32/89_2.png) [@jyoung](https://community.sonatype.com/u/jyoung)\
**Post date:** [April 29, 2020, 5:03pm UTC](https://community.sonatype.com/t/node-js-support-through-the-nexus-iq-ide-plugins/4014/2 "2020-04-29T17:03:53Z")

</div>

We are currently investing in [IQ for SCM](https://help.sonatype.com/integrations/nexus-iq-for-scm) which provides a centralized view of policy results and component information in a tool where developers can collaborate. As such, we have no plans on the roadmap to add additional language support to the IDEs. Which features about the IDE plugins do you find crucial to software development? I’m interested to understand the feasibility of us providing those in SCM.

As a side note, there is a [VS Code extension](https://github.com/sonatype-nexus-community/vscode-iq-plugin) provided by the community that has support for Node.js.

---

<div class="post-metadata">

**Author:** ![steven.j.doubleday](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@steven.j.doubleday](https://community.sonatype.com/u/steven.j.doubleday)\
**Post date:** [April 29, 2020, 7:58pm UTC](https://community.sonatype.com/t/node-js-support-through-the-nexus-iq-ide-plugins/4014/3 "2020-04-29T19:58:55Z")

</div>

It seems to me that both IDE support and SCM support at pull-request time are useful. The nice thing about having a plug-in in the IDE is that from the moment I open a project, I can see what the current problems are, and start in on them.  
If I don’t have that visibility, I might start coding and generate one or a series of commits, before creating a pull request, only to discover that there are issues that would prevent me from merging. I’d like to know as early as possible, and use the pull  
request mechanism to make sure nothing slips through the cracks.

I’d encourage you not to put all your effort into SCM at the expense of the IDE’s.

I found the VS Code extension you mentioned, and it’s very useful.

Steve