<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Garrett Poell on Medium]]></title>
        <description><![CDATA[Stories by Garrett Poell on Medium]]></description>
        <link>https://medium.com/@gpoell.gp?source=rss-70089b049806------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HnXbv4_fVSM4nyPy.jpg</url>
            <title>Stories by Garrett Poell on Medium</title>
            <link>https://medium.com/@gpoell.gp?source=rss-70089b049806------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 23 May 2026 16:23:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gpoell.gp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Bash: Node: Command Not Found]]></title>
            <link>https://medium.com/@gpoell.gp/bash-node-command-not-found-ff33886acda?source=rss-70089b049806------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff33886acda</guid>
            <category><![CDATA[command-not-found]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[bash]]></category>
            <dc:creator><![CDATA[Garrett Poell]]></dc:creator>
            <pubDate>Fri, 28 Feb 2020 20:56:12 GMT</pubDate>
            <atom:updated>2020-02-28T20:56:12.800Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An image of Node’s logo" src="https://cdn-images-1.medium.com/max/750/1*Io6-4qVNzurePcByKeNCng.jpeg" /><figcaption>Bash:Node: Command Not Found</figcaption></figure><p>I ran into this problem the other day when cleaning up and reorganizing the files on my computer. Here is a quick post on how to resolve the infamous bash error due to the environment PATH variable not being correctly defined:</p><blockquote>-bash: node: command not found</blockquote><p>The problem is most likely that your $PATH (environment variable) is not pointing to the correct location of where you downloaded or moved Node. Regardless of what happened, updating your $PATH is simple.</p><h3><strong>Solution</strong></h3><p>Update your $PATH to include the correct location to Node. An example of your node location might look like this:</p><blockquote>C:\Program Files\nodejs</blockquote><p>There are ways to update your PATH through the command line, but for those who do not feel comfortable with that method, I have provided a way to do it through your Control Panel where you can visualize what’s happening.</p><p>Depending on your operating system (e.g. Mac, Windows, Linux, etc..) and the version (e.g. Windows 7, 8, 10), the process for updating the PATH variable will be different. Java has a great article on how to get to your environment variables depending on your operating system that I would recommend following if my instructions below don’t apply to you.</p><p><a href="https://www.java.com/en/download/help/path.xml">How do I set or change the PATH system variable?</a></p><h4><strong>Windows 10 Solution</strong></h4><p>Below are the steps to get to where you need to update your PATH if your computer is running Windows.</p><p>The fastest way to get to your <strong>environment variables </strong>is to type in the search bar in the bottom left corner of your screen. From there you will proceed to locate your <strong>Path</strong> and add/update your path to Node.</p><figure><img alt="An example of how to search for editing the environment variables" src="https://cdn-images-1.medium.com/max/834/1*9HfmQs90oxLNTUkmWS7UTA.png" /><figcaption>Edit the system environment variables</figcaption></figure><figure><img alt="Environment Variables Panel" src="https://cdn-images-1.medium.com/max/618/1*SO4gr_yHN-vco8Hi_1mQAA.png" /><figcaption>Environment Variables</figcaption></figure><figure><img alt="Edit the environment variables" src="https://cdn-images-1.medium.com/max/527/1*fmBaJVuvsvYlYKXdL_rmQg.png" /><figcaption>Edit Environment Variable</figcaption></figure><figure><img alt="File location of Node to copy and paste into your environment variable path" src="https://cdn-images-1.medium.com/max/1024/1*eGUMuQJPXaOulzWDRdirMg.png" /><figcaption>Copy and paste the path to Node into your $PATH environment variable</figcaption></figure><p>Once your $PATH is updated, open up a new bash session and you should be good to go. Feel free to comment with other solutions if this didn’t work for you, but I hope this helps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff33886acda" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>