<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Development-Environment on hobbyworker취미생활자</title>
    <link>https://hobbyworker.me/en/tags/development-environment/</link>
    <description>Recent content in Development-Environment on hobbyworker취미생활자</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>2026 hobbyworker</copyright>
    <lastBuildDate>Sat, 18 Mar 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hobbyworker.me/en/tags/development-environment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Managing Multiple Node.js Environments with NVM</title>
      <link>https://hobbyworker.me/en/dev/2023-03-18-managing-multiple-nodejs-environments-with-nvm/</link>
      <pubDate>Sat, 18 Mar 2023 00:00:00 +0000</pubDate>
      <guid>https://hobbyworker.me/en/dev/2023-03-18-managing-multiple-nodejs-environments-with-nvm/</guid>
      <description>In summary, this blog post discussed Node Version Manager (NVM), a valuable tool for developers to manage and switch between multiple Node.js versions. The post provided installation instructions for macOS, Linux, and other Unix-based systems, and covered the top 10 most commonly used features of NVM, such as listing available Node.js versions, installing, switching, setting a default version, uninstalling, and running scripts and commands with a specific version. NVM enables developers to efficiently work with different Node.js versions, ensuring seamless testing and compatibility across various projects and environments.</description>
    </item>
  </channel>
</rss>
