---
title: "Configuring Node.js Workspaces in Coder - Blog - Coder"
description: "Workspaces can be automated to clone git repos, install a specific versions of Node / global packages, set environment variables, and more."
image: "/api/dynamic-og?title=Configuring+Node.js+Workspaces+in+Coder&randomBackground=true&styles=%7B%22height%22%3A162%2C%22width%22%3A302%2C%22padding%22%3A16%2C%22titleSize%22%3A24%2C%22logo%22%3A%7B%22width%22%3A80%2C%22height%22%3A12.15%7D%7D"
canonical: "https://coder.com/blog/configuring-node-js-workspaces-in-coder"
---

May 25 20211 min read

# Configuring Node.js Workspaces in Coder

[Ben Potter](https://coder.com/blog/author/bpmct)

Share this article

As a developer advocate at Coder, I’m often starting new projects and improving old demos, with Node.js being my language of choice. Coder’s been great for this, as I know that anyone (including myself in a few months) can continue where I left off: inside a cloud dev environment that just works, with all of the correct dependencies.

Coder provides a [default Node.js image](https://github.com/cdr/enterprise-images/tree/main/images/node), which is great for the basics. However, workspaces can be further automated to clone git repos, install specific versions of Node / global packages, set environment variables, and more.

After building a few custom workspaces, I figured I’d write a guide and share some of the things I’ve learned: [https://coder.com/docs/guides/customization/node](https://coder.com/docs/guides/customization/node)

Have questions, or an interesting use case for Coder? Let us know about it on Twitter [@CoderHQ](https://twitter.com/coderhq) or [Slack](https://cdr.co/join-community).

### Subscribe to our newsletter

Want to stay up to date on all things Coder? Subscribe to our monthly newsletter for the latest articles, workshops, events, and announcements.