<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: DEVEV</title>
    <description>The latest articles on DEV Community by DEVEV (@devev01).</description>
    <link>https://dev.to/devev01</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1008943%2Fc71e6a83-2864-490c-acd4-48c0818ae8ea.png</url>
      <title>DEV Community: DEVEV</title>
      <link>https://dev.to/devev01</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/devev01"/>
    <language>en</language>
    <item>
      <title>Git) Checkout Remote Branch</title>
      <dc:creator>DEVEV</dc:creator>
      <pubDate>Wed, 25 Jan 2023 05:02:10 +0000</pubDate>
      <link>https://dev.to/devev01/git-checkout-remote-branch-483k</link>
      <guid>https://dev.to/devev01/git-checkout-remote-branch-483k</guid>
      <description>&lt;h2&gt;
  
  
  When to checkout git remote branch?
&lt;/h2&gt;

&lt;p&gt;When the remote branch already existed, and you want to pull the branch and its changes to your local environment.&lt;/p&gt;



&lt;h2&gt;
  
  
  How to checkout git remote branch?
&lt;/h2&gt;

&lt;p&gt;It depends on whether there is one configured remote repository or multiple repositories.&lt;/p&gt;

&lt;h4&gt;
  
  
  With Single Remote Repository
&lt;/h4&gt;

&lt;h5&gt;
  
  
  1. Fetch all remote branches
&lt;/h5&gt;

&lt;h6&gt;
  
  
  Start by fetching all the latest changes from remote repository
&lt;/h6&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ git fetch

# alternatives(depends on your remote name)
$ git fetch origin 
$ git fetch upsteam
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h5&gt;
  
  
  2. Check all branches available for checkout
&lt;/h5&gt;

&lt;h6&gt;
  
  
  -v(verbose): show extra info
&lt;/h6&gt;

&lt;h6&gt;
  
  
  -a(all): list all
&lt;/h6&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ git branch -v -a
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h5&gt;
  
  
  3. Checkout to the remote branch
&lt;/h5&gt;

&lt;h6&gt;
  
  
  Now you can checkout and  track the remote branch
&lt;/h6&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ git switch &amp;lt;branch name&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h4&gt;
  
  
  With Multiple Remote Repositories
&lt;/h4&gt;

&lt;h5&gt;
  
  
  1. Fetch all remote branches
&lt;/h5&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ git fetch

# alternatives(depends on your remote name)
$ git fetch origin 
$ git fetch upsteam
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h5&gt;
  
  
  2. Check all branches available for checkout
&lt;/h5&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ git branch -v -a
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h5&gt;
  
  
  3. Checkout to the remote branch
&lt;/h5&gt;

&lt;h6&gt;
  
  
  In case where multiple remotes exist, the remote repositories should be explicitly named.
&lt;/h6&gt;

&lt;h6&gt;
  
  
  Checkout the branch with -c option to create new local branch
&lt;/h6&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ git switch -c &amp;lt;branch name&amp;gt; origin/&amp;lt;branch name&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
    </item>
    <item>
      <title>Vue CLI Guide</title>
      <dc:creator>DEVEV</dc:creator>
      <pubDate>Tue, 17 Jan 2023 01:02:29 +0000</pubDate>
      <link>https://dev.to/devev01/vue-cli-guide-5al4</link>
      <guid>https://dev.to/devev01/vue-cli-guide-5al4</guid>
      <description>&lt;h2&gt;
  
  
  Vue CLI Overview
&lt;/h2&gt;

&lt;p&gt;Vue CLI is the easiest way to build a new Vue app.&lt;br&gt;
It provides:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a command-line utility for you to choose build tools&lt;/li&gt;
&lt;li&gt;official plugins&lt;/li&gt;
&lt;li&gt;runtime dependency built on top of webpack with sensible defaults&lt;/li&gt;
&lt;/ul&gt;



&lt;h2&gt;
  
  
  Installation &amp;amp; Update
&lt;/h2&gt;

&lt;p&gt;Run one of the following commands.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Vue CLI 4.x requires Node.js version 8.9 or above. Manage multiple versions of Node with nvm.&lt;br&gt;
&lt;/p&gt;


&lt;/blockquote&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ npm install -g @vue/cli
# OR
$ yarn global add @vue/cli
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Check if you did it right↓&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ vue --version
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To upgrade the global Vue CLI package, run↓&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ npm update -g @vue/cli
# OR
$ yarn global upgrade --latest @vue/cli
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;h2&gt;
  
  
  Creating a Project
&lt;/h2&gt;

&lt;p&gt;To create a new project, run↓&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ vue create &amp;lt;project name&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and you'll be prompted to pick a preset. You can either choose the default preset or select "Manually select features" to pick the versions and features you need.&lt;/p&gt;



&lt;h2&gt;
  
  
  Troubleshooting
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Vue command not found error after installation
&lt;/h3&gt;
&lt;h4&gt;
  
  
  a. Uninstall vue/cli and install it again&lt;br&gt;
&lt;/h4&gt;

&lt;p&gt;(and then restarting terminal recommended)&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ npm uninstall -g @vue/cli
# OR
$ yarn global remove @vue/cli
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the globall installation fails, try running command with prefix 'sudo'.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ sudo npm uninstall vue-cli -g
$ sudo npm install -g @vue/cli
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  b. Uninstall and install node again with the right version
&lt;/h4&gt;

&lt;p&gt;check installed node version↓&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ node --verison
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://codedamn.com/news/nodejs/how-to-uninstall-node-js" rel="noopener noreferrer"&gt;How to uninstall Node.js completely&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  c. Add PATH environment variable
&lt;/h4&gt;

&lt;p&gt;Run following command to see where npm puts your globally installed packages.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ npm config get prefix
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# output example(windows)
# C:\Users\{UserName}\AppData\Roaming\npm
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Check if your operating system has the PATH environment variable. If not, add the path you got from the command above.&lt;/p&gt;

&lt;h4&gt;
  
  
  How to add PATH environment variable on WINDOWS
&lt;/h4&gt;

&lt;p&gt;Open command promt(windows key + R) and run command↓&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ set
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It will show you PATHs added to your OS. Try update it on Windows Control Panel.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Control Panel &amp;gt; System and Security &amp;gt; System &amp;gt; Advanced system settings &amp;gt; Environment Variables...&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Frd8qfbyf69iwakop4900.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Frd8qfbyf69iwakop4900.png" width="645" height="735"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://phoenixnap.com/kb/linux-add-to-path" rel="noopener noreferrer"&gt;How to add PATH environment variable on LINUX&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stackoverflow.com/questions/40317578/yarn-global-command-not-working" rel="noopener noreferrer"&gt;How to export PATH to ~/.bash_profile&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;
  
  
  Sources
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://cli.vuejs.org/" rel="noopener noreferrer"&gt;https://cli.vuejs.org/&lt;/a&gt;&lt;br&gt;
&lt;a href="https://bobbyhadz.com/blog/npm-command-not-found-vue" rel="noopener noreferrer"&gt;https://bobbyhadz.com/blog/npm-command-not-found-vue&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cryptocurrency</category>
      <category>bitcoin</category>
      <category>blockchain</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
