<?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>Forem: Naveen Bantu</title>
    <description>The latest articles on Forem by Naveen Bantu (@naveenbantu).</description>
    <link>https://forem.com/naveenbantu</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%2F1102204%2Fa50a975a-bbec-4e72-b43b-07f11aa312a3.png</url>
      <title>Forem: Naveen Bantu</title>
      <link>https://forem.com/naveenbantu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/naveenbantu"/>
    <language>en</language>
    <item>
      <title>Embrace the Power of the Cloud: Deploying a MERN Stack Application with Vercel</title>
      <dc:creator>Naveen Bantu</dc:creator>
      <pubDate>Sat, 01 Jul 2023 15:49:30 +0000</pubDate>
      <link>https://forem.com/naveenbantu/embrace-the-power-of-the-cloud-deploying-a-mern-stack-application-with-vercel-2gob</link>
      <guid>https://forem.com/naveenbantu/embrace-the-power-of-the-cloud-deploying-a-mern-stack-application-with-vercel-2gob</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Welcome to the dynamic realm of web development, where businesses strive to establish their digital presence. In this age of innovation, one stack has distinguished itself from the competition, captivating developers with its ability to produce robust web apps. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Say hello to the MERN stack!!!&lt;/strong&gt;, the unbeatable combination of MongoDB, Express.js, React.js, and Node.js. This tech quartet empowers developers to craft feature-rich applications that seamlessly merge scalability and efficiency.&lt;/p&gt;

&lt;p&gt;However, building a MERN stack application is only one part of the equation. Deploying it to a production environment can be a daunting task, requiring careful configuration and management. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vercel&lt;/strong&gt; to the rescue. Vercel is a cloud platform that simplifies the deployment and hosting process, making it an ideal choice for MERN stack applications.&lt;/p&gt;

&lt;p&gt;In this blog post, we will explore the seamless experience of deploying a MERN stack application using Vercel. We'll discuss:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Benefits of using Vercel&lt;/li&gt;
&lt;li&gt;Preparing MERN stack application for Deployment&lt;/li&gt;
&lt;li&gt;Walk through the deployment process step-by-step&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Why Choose Vercel?
&lt;/h3&gt;

&lt;p&gt;Vercel provides a comprehensive platform for deploying modern web applications effortlessly. Here are a few reasons why it has gained immense popularity among developers:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Easy Setup:&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Vercel offers a straightforward setup process, allowing developers to deploy their MERN stack applications with just a few clicks. &lt;/li&gt;
&lt;li&gt;It eliminates the need for manual configurations and reduces the time required to get your application up and running.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Continuous Deployment:&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;By enabling automatic deployments with Vercel, you can be sure that every change you push to your repository results in a fresh deployment. &lt;/li&gt;
&lt;li&gt;This enables a seamless and continuous delivery process, keeping your application up-to-date.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Scalability:&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Vercel harnesses the power of serverless functions and edge caching.&lt;/li&gt;
&lt;li&gt;Enables effortless scalability for MERN stack applications.&lt;/li&gt;
&lt;li&gt;Ensures optimal performance even under high traffic volumes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Global CDN:&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Vercel provides a global content delivery network (CDN) that ensures your application is delivered quickly to users worldwide. &lt;/li&gt;
&lt;li&gt;This optimizes the user experience by reducing latency and improving overall performance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Serverless Functions:&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The use of serverless functions allows for efficient handling of dynamic data processing and offloading heavy computation tasks.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Preparing MERN stack application for Deployment
&lt;/h3&gt;

&lt;p&gt;Before deploying our app, let's make sure we have the right configurations in place. The following configuration steps are needed:&lt;/p&gt;

&lt;h4&gt;
  
  
  Step 1:
&lt;/h4&gt;

&lt;p&gt;The backend folder should be renamed to &lt;strong&gt;&lt;em&gt;"api"&lt;/em&gt;&lt;/strong&gt; and the main js file should be named &lt;strong&gt;&lt;em&gt;"index.js"&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--j9mu2BSX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://ik.imagekit.io/hashinsert/Change_Name_Server.png%3FupdatedAt%3D1688166195754" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--j9mu2BSX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://ik.imagekit.io/hashinsert/Change_Name_Server.png%3FupdatedAt%3D1688166195754" alt="Image description" width="660" height="864"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Step 2:
&lt;/h4&gt;

&lt;p&gt;Every controller should be having a connection to the database. This is because each controller will be deployed as a Serverless function.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Inside &lt;strong&gt;&lt;em&gt;"api"&lt;/em&gt;&lt;/strong&gt; folder, create a &lt;strong&gt;&lt;em&gt;"config"&lt;/em&gt;&lt;/strong&gt; folder add &lt;strong&gt;&lt;em&gt;"db.js"&lt;/em&gt;&lt;/strong&gt; file with the following code.&lt;br&gt;
&lt;/p&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nx"&gt;mongoose&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;mongoose&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;connectDB&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;try&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;conn&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;mongoose&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;connect&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;MONGO_URI&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="nx"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;`MongoDB Connected: &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;conn&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;connection&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;host&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;catch &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;error&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;error&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;`Error: &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;error&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;message&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;exit&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="nx"&gt;connectDB&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/li&gt;
&lt;/ul&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Import and call the &lt;strong&gt;&lt;em&gt;"connectDB"&lt;/em&gt;&lt;/strong&gt; in all the controller functions.&lt;br&gt;
&lt;/p&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;getMocks&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;next&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// Connecting to mongoDB&lt;/span&gt;
    &lt;span class="nf"&gt;connectDB&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;

    &lt;span class="k"&gt;try&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="c1"&gt;//...code block fetching the mocks&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;catch &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;error&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="c1"&gt;//...handling errors&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  Step 3:
&lt;/h4&gt;

&lt;p&gt;Create a &lt;strong&gt;&lt;em&gt;"vercel.json"&lt;/em&gt;&lt;/strong&gt; and add the following configuration.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"buildCommand"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"cd client &amp;amp;&amp;amp; yarn install &amp;amp;&amp;amp; ./node_modules/vite/bin/vite.js build"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"outputDirectory"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"client/dist"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"framework"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"vite"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"rewrites"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"source"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"/api/(.*)"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"destination"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"/api/index.js"&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"source"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"/(.*)"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"destination"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"/index.html"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;blockquote&gt;
&lt;p&gt;Break down of each configuration option:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;em&gt;buildCommand&lt;/em&gt;&lt;/strong&gt;: This option specifies the command to build the client-side application. In this case, the build command is:
&lt;code&gt;cd client &amp;amp;&amp;amp; yarn install &amp;amp;&amp;amp; ./node_modules/vite/bin/vite.js build&lt;/code&gt;

&lt;ul&gt;
&lt;li&gt;Changes the directory to the client folder&lt;/li&gt;
&lt;li&gt;Installs the required dependencies using yarn install &lt;/li&gt;
&lt;li&gt;Builds the application using the Vite build command.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;em&gt;outputDirectory&lt;/em&gt;&lt;/strong&gt;: This option determines the directory where the built application will be stored. In this case, it is set to &lt;code&gt;client/dist&lt;/code&gt;, indicating that the built files will be placed in the client/dist folder.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;em&gt;framework&lt;/em&gt;&lt;/strong&gt;: This option specifies the framework used by the application. In this configuration, the framework is set to &lt;code&gt;vite&lt;/code&gt;, indicating that the application is built using Vite.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;em&gt;rewrites&lt;/em&gt;&lt;/strong&gt;: This option defines a list of URL rewrite rules for routing requests. The rules are processed in the order they appear. In this configuration, there are two rewrite rules:

&lt;ul&gt;
&lt;li&gt;The first rewrite rule specifies that any requests starting with &lt;code&gt;/api/&lt;/code&gt; should be rewritten to &lt;code&gt;/api/index.js&lt;/code&gt;. This is commonly used to redirect API requests to serverless functions.&lt;/li&gt;
&lt;li&gt;The second rewrite rule states that for any other requests &lt;code&gt;(/(.*))&lt;/code&gt;, the destination should be &lt;code&gt;/index.html&lt;/code&gt;. This is typically used for client-side routing, where the application's main index.html file is served for all routes to allow the client-side router to handle the routing within the application.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;h3&gt;
  
  
  Deployment Process with Vercel:
&lt;/h3&gt;

&lt;p&gt;Following is a step-by-step guide to deploy your MERN stack application with Vercel:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 1:&lt;/strong&gt; Sign up for a Vercel account. Then Log in to Vercel dashboard, click on the “Add New…” button, and select the “Project” category.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 2:&lt;/strong&gt; Connect your MERN stack application repository to Vercel. &lt;em&gt;(Vercel supports various version control systems like Git, GitHub, and GitLab)&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Select your Git repository and choose the branch you want to deploy.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Step 3:&lt;/strong&gt; Configure your deployment settings. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The framework and build settings are &lt;strong&gt;already configured&lt;/strong&gt; in the &lt;strong&gt;&lt;em&gt;"vercel.json"&lt;/em&gt;&lt;/strong&gt; for your MERN stack application.&lt;/li&gt;
&lt;li&gt;Add all the environment variables, both "client" and "api" related.
&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;    &lt;span class="nv"&gt;MONGO_URI&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&amp;lt;your-mongo-URI&amp;gt;
    &lt;span class="nv"&gt;PORT&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;5050
    &lt;span class="nv"&gt;CLERK_SECRET_KEY&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&amp;lt;your-clerk-secret-key&amp;gt;
    &lt;span class="nv"&gt;VITE_REACT_APP_CLERK_PUBLISHABLE_KEY&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&amp;lt;your-clerk-public-key&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;&lt;strong&gt;Step 4:&lt;/strong&gt; Review and CLICK on the &lt;strong&gt;&lt;em&gt;Deploy&lt;/em&gt;&lt;/strong&gt; button. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 5:&lt;/strong&gt; After successfully deploying the MERN application, the &lt;strong&gt;FINAL&lt;/strong&gt; step is to add the &lt;strong&gt;Deployed URL&lt;/strong&gt; as environment variable for the Client API calls.&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;VITE_REACT_API_URL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;https://mockmeet-vercel.vercel.app/api
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;blockquote&gt;
&lt;p&gt;For example: In Mockmeet, we are using an Environment variable "VITE_REACT_API_URL" to connect the frontend to the API endpoints.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;After adding the deployed URL as an environment variable, re-deploy your application.&lt;/p&gt;


&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;a href="https://scribehow.com/shared/Deploying_MERN_app_on_Vercel__ymLtmsBERcCFB4lHh_il1w" rel="noopener noreferrer"&gt;
      scribehow.com
    &lt;/a&gt;
&lt;/div&gt;



&lt;h4&gt;
  
  
  &lt;strong&gt;Congratulations!&lt;/strong&gt;🎊 Your MERN stack application will be up and running within a few minutes after deployment.
&lt;/h4&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>deploy</category>
      <category>mern</category>
    </item>
  </channel>
</rss>
