<?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-Workflow on hobbyworker취미생활자</title>
    <link>https://hobbyworker.me/en/tags/development-workflow/</link>
    <description>Recent content in Development-Workflow on hobbyworker취미생활자</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>2026 hobbyworker</copyright>
    <lastBuildDate>Thu, 23 Mar 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hobbyworker.me/en/tags/development-workflow/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using NVM and Autoenv in Combination</title>
      <link>https://hobbyworker.me/en/dev/2023-03-23-using-nvm-and-autoenv-in-combination/</link>
      <pubDate>Thu, 23 Mar 2023 00:00:00 +0000</pubDate>
      <guid>https://hobbyworker.me/en/dev/2023-03-23-using-nvm-and-autoenv-in-combination/</guid>
      <description>we discussed how to combine nvm (Node Version Manager) and autoenv to manage Node.js versions and environment variables seamlessly in your development workflow. By creating an .env file with the desired Node.js version and environment variables, and configuring autoenv to work with nvm, you can automatically switch Node.js versions and load appropriate variables when navigating between projects. This streamlined approach can significantly enhance your development process, ensuring that you&amp;#39;re always using the correct settings for each project.</description>
    </item>
  </channel>
</rss>
