DEV Community: Shafia Rahman Chowdhury

Digital Marketing AI Coach

Shafia Rahman Chowdhury — Sat, 05 Jul 2025 19:14:54 +0000

This is a submission for the Runner H "AI Agent Prompting" Challenge

What I Built

I built a Digital Marketing AI Coach using Runner H that acts as a weekly performance coach for each member of my digital marketing team. It helps track how each member is doing based on their content submissions, deadlines, and social media engagement, and sends them custom tips to improve, along with creative content suggestions for next week.

This agent not only saves me hours of reviewing content sheets and giving feedback but also keeps the whole team motivated and improving, week by week.

As someone managing a content team, I face these problems every week:

Some team members post content on our dedicated social media platforms late or miss deadlines
Not all content gets the engagement we expect
It's hard to give personalized, timely feedback to everyone
Creativity drops when people don’t know what to post next

Instead of doing everything manually, I wanted a solution that could analyze performance, suggest improvements, and boost creativity for each member.

Demo

Here is the PDF generated by Runner H: Digital Marketing AI Coach

The screenshot of the automated mail sent and Runner H
https://drive.google.com/drive/folders/1LBSHpE7Hsr6VtE1YS0lPBweqTeaJdbno?usp=sharing

How I Used Runner H

Runner H acts as my AI content strategist.

It reads our shared Google Sheet where we track content types, deadlines, engagement (likes), and whether each post was missed or not. Then for each person, Runner H:

Analyzes:

How many tasks they completed per month compared to the given tasks per month (according to KPI)
Which were late
What kind of content performed best/worst

Generates a personalized report:

Performance summary of each member
Give improvement suggestions to the members
Suggests one creative challenge to try (I call it a “Strategy Spin Card”)

Sends that report directly to the team member (via email)
Then it creates a manager summary:

Top performer of the week
Missed deadlines overview
What content types are working best
Suggests what to improve across the team

The Prompt I Gave Runner H

Access the Google Sheet at:

[Insert Google Sheet Link]

This sheet contains the following columns:

Deadline | Posted Date | Content Type | Topic | Platform | Assigned To | Status | Is Missed | Likes | Rating

TASK 1: Individual Performance Reports
For each unique person in the "Assigned To" column:

- Analyze their weekly data:
- Total content pieces submitted
- Number of missed deadlines (Is Missed = Yes)
- Average engagement (Likes)
- Highest- and lowest-performing content types (based on Likes)

Generate a personalized weekly report that includes:

- What they did well
- What they need to improve
- Two new content ideas for next week based on:
- Their strong formats
- Weak engagement areas
- Platform trends

A randomly assigned "Strategy Spin Card" from:

“Use a trending reel audio”

“Post a behind-the-scenes video”

“Ask a thought-provoking poll”

“Turn a meme into a carousel”

“Start your post with a question”

Send the report to each person via email. [email]


TASK 2: Manager Weekly Summary

Generate a summary email/report for the team manager that includes:

Stats:

- Total content published this week
- Overall engagement average
- Overall % of deadlines met (vs missed)
- Top 3 most used content types

Highlights:

- Top performer (by average Likes)
- Most improved member (compared to last week)
- Most effective content type (team-wide)

 Recommendations:

- If engagement is down, suggest new post types
- If one format is repeated too much, suggest variety

OUTPUT FORMAT

Send each team member a friendly message with their personal stats, tips, and creativity challenge.


OBJECTIVE
Keep the team aligned, inspired, and improving using weekly performance insights and creative nudges.

Encourage content diversity and reduce the manager workload.

Use Case & Impact

Use Case

Who It’s For:

Team leads or managers who oversee content creators, interns, or marketing teams
Startups or small businesses relying on consistent social media presence
Creative teams needing structured, weekly performance insights
Organizations that track content output via Google Sheets or Notion but struggle with timely feedback and motivation

What It Solves:

Lack of real-time, personalized feedback for team members
Time-consuming manual performance tracking and reviews
Team members unsure of what content types to try next
Missed deadlines and inconsistent creativity
No visibility into what’s actually working on social media

Impact

For Managers:

Saves 3–5 hours weekly on performance reviews
Eliminates the need to manually check content metrics
Offers a clear team-wide performance snapshot every week
Makes it easy to track progress and see who needs support
Encourages a growth-focused culture, not just output

For Team Members:

Receives personalized coaching without feeling micromanaged
Gains insight into what content worked or didn’t, with reasons
Feels more motivated and accountable thanks to weekly feedback
Gets new, fun content suggestions to stay creative
Encouraged to experiment and level up their strategy

For the Brand:

Increases content quality and consistency
Boosts overall engagement through data-informed strategy
Ensures the team is aligned with goals and creative direction
Promotes continuous improvement in a lightweight, human-friendly way

Facing authentication errors on GitHub? Check out this blog for a step-by-step guide to resolving it!

Shafia Rahman Chowdhury — Tue, 03 Dec 2024 17:00:03 +0000

Support for password authentication was removed. Please use a personal access token instead.

Shafia Rahman Chowdhury ・ Jul 4 '23

Error-: src refspec main does not match

Shafia Rahman Chowdhury — Wed, 03 Jan 2024 08:00:23 +0000

Error-: src refspec main does not match any

This error message usually indicates that the branch you're attempting to push does not exist.

Solution-1

Check if you have missed the command git add . or git commit -m"message. If so, then delete the terminal and write the git commands again.

Solution-2

Step 1: Go to GitHub Settings and then go to Emails

Step-2: Uncheck Keep my email addresses private

Step-3: Push your code again

Solution-2

Open your Git bash terminal and run the following commands one by one:



rm -rf .git
git init
git add .
git commit -m "added"
git branch -M main
git remote add origin <YOUR_GITHUB_REPO_LINK>
git push -u origin main -f


Happy Coding!

Error: (e.g git pull..) before pushing again

Shafia Rahman Chowdhury — Mon, 01 Jan 2024 14:28:34 +0000

The error below takes place when you edit your file directly from github as a result code in local file and file github file does not match.

Go to your terminal again and run these commands

Solution-1

git pull
git push origin main

Solution-2 (not recommended)

git push -f

By following these steps, you should be able to synchronize your local changes with the changes on GitHub and avoid conflicts.

Requested URL returned error: 403

Shafia Rahman Chowdhury — Mon, 01 Jan 2024 13:46:58 +0000

The image below shows a 403 error which means means credentials errors or forbidden (you don’t have permission to push).

Solution-1

Step-1: Check if you are pushing the code to your repository

git remote -v

Step-2: If it is not your repository, open a new repository in your GitHub

Step-3: Copy your repository link

Step-4: Go to the terminal and write the following command:

git remote set-url origin your-repo-link

After the entering command, check if the git repository url changed. Write git remote -v on your terminal.

Step-5: Then, run these commands one by one

git branch -M main
git push -u origin main

Solution-2

Step-1: Go to your Start tab on windows and search for Credential Manager.

Step-2: Click on the Credential Manager and then click on Windows Credential

Step-3: Below, Generic Credentials you will see git:https://github.com. Remove it.

Step-4 Follow the steps in this blog
https://dev.to/shafia/support-for-password-authentication-was-removed-please-use-a-personal-access-token-instead-4nbk

Take your JavaScript skills to the next level with these 10 GitHub repositories 🕵️‍♂️ 🚀

Shafia Rahman Chowdhury — Tue, 03 Oct 2023 12:57:26 +0000

এই ব্লগটিতে, ১০টি helpful গিটহাব links দেওয়া হয়েছে। JavaScript skills যদি next level এ নিয়ে যেতে চান then explore the repositories given below. It's worth your time!!! 🕰

1. JavaScript questions 🤔

এই repository তে আছে:

কোডিং রিলেটেড interview questions,
আপনার JS knowledge brush up হবে,
কতো ভালো JS পারেন সেটা assess করতে পারবেন

এখানে basic থেকে advanced level এর questions আছে এবং প্রতিটা questions এর নিচে correct answer & explanation দেওয়া হয়েছে যেটা ক্লিক করলে দেখতে পারবেন। (Do not see the answer before trying!👀)

2. 33 Concepts Every JavaScript Developer Should Know 👨🏻‍🏫

৩৩টা concept নিয়ে এই repository তৈরি করা হয়েছে।একটা ভালো JavaScript Developer হতে চাইলে এই concept গুলো জানা খুব দরকার।

এই repository আছে:

Articles,
Videos,
Books

3. WTFJS 😮

JavaScript এর কিছু tricky concepts আছে যেটা অনেকের বুঝতে difficult হয়, especially for the beginners. যেমন ধরেনঃ

NaN === NaN; // -> false

false কেন??

এই repository তে আছে

tricky concepts examples with detailed explanation

4. You don't know JS 🤯

যদি JavaScript সম্পর্কে in-depth knowledge grow করতে চান তাহলে এই repository ফলো করতে পারেন। এখানে JavaScript এর core mechanism নিয়ে detailed explanation আছে

এখানে আছেঃ

Kyle Simpson's এর 1st & 2nd editions book (completely free!)

5. Airbnb JavaScript style guide 🤩

এই repository টা খুব popular internet এ। এখানে কিছু set of guidelines & best practices আছে।It's written by the Airbnb team!😱

এখানে আছে :

good code & bad code with explanation
recommendations on various JS topics

6. Tech interview handbook 👩‍💻

500,000 people এই repository টা follow করে benefitted হয়েছে। Tech interview জন্য এখানে কিছু useful resources দেওয়া হয়েছে।

এখানে আছে :

content covering all phases of a technical interview, from applying for a job to passing the interviews to offer negotiation.

Totally worth checking out!

7. The Algorithm - Javascript 📱

Competitive programming এর জন্য খুব হেল্পফুল এবং internet এ বেশ জনপ্রিয়। মাঝে মাঝে কিছু algorithms/data structures নিয়ে interview তে question করে তাই এই repository টা explore করা recommended।

এখানে আছে :

data structures & algorithm implementation
algorithms from the basic sorting and searching to complex ones such as dynamic programming.

8. Awesome JavaScript 🔥

এখানে আছে links to useful:

package managers,
loaders,
bundlers and transpilers to UI tools,
utilities,
gestures,
maps,
animation, etc.

This can be one of most useful resource out there if you take proper advantage of it!

9. Effective Engineer Notes 👩‍🔧

একজন effective engineer কিভাবে হতে পারবেন সেটা নিয়ে কিছু guidelines এই repository তে দেওয়া হয়েছে। এটা ফলো করলে আপনার decision-making and logical thinking আরও বেটার হবে।

10. Free programming books 📚

এখানে collection of useful books & tutorials দেওয়া হয়েছে। খুব famous একটা repository এবং GitHub এ 271,000+ stars আছে.🤯

Happy exploring!👋

Authentication and Authorization

Shafia Rahman Chowdhury — Tue, 03 Oct 2023 08:37:19 +0000

Authentication এবং Authorization মৌলিকভাবে বিভিন্ন ফাংশন উপস্থাপন করে, যদিও প্রায়শই তারা interchangeably ব্যবহৃত হয়। এই আর্টিকেলে, আমরা দুটির আলোচনা, তুলনা ও বৈসাদৃশ্য করি তা দেখানোর জন্য যে তারা কীভাবে complementary উপায়ে অ্যাপ্লিকেশনগুলিকে রক্ষা করে। তবে, তার আগে আমরা আরেকটা জিনিস সম্পর্কে সাধারণ ধারণা জেনে নি। সেটি হলো Introduction to Identity and Access Management (IAM)।

Identity and Access Management (IAM) কি?

IAM বোঝার জন্য, আপনাকে কিছু মৌলিক ধারণার সাথে পরিচিত হতে হবে:

একটি digital resource (ডিজিটাল রিসোর্স) হল একটি কম্পিউটার সিস্টেমে অ্যাপ্লিকেশন এবং ডেটার যে কোনো সমন্বয়/combination। ডিজিটাল রিসোর্সের উদাহরণগুলির মধ্যে রয়েছে ওয়েব অ্যাপ্লিকেশন, APIs, প্ল্যাটফর্ম, ডিভাইস বা ডেটাবেস।
আইএএম এর মূল হল Identity। কেউ আপনার ডিজিটাল রিসোর্সের অ্যাক্সেস চায়। এটি একজন customer, employee, member, participant এবং আরও অনেক কিছু হতে পারে। আইএএম-এ, একটি ব্যবহারকারী অ্যাকাউন্ট হচ্ছে একটি ডিজিটাল আইডেন্টিটি বা পরিচয়। ব্যবহারকারীর অ্যাকাউন্টগুলি non-human কেও represent করতে পারে, যেমন সফ্টওয়্যার, ইন্টারনেট অফ থিংস ডিভাইস বা রোবোটিক্স৷

Authentication হল একটি ডিজিটাল আইডেন্টিটি verification। যখন ইউজাররা authenticate করে তখন তারা ঐ সাইটে বা অ্যাপে এইটা prove করে যে তারা সেই ব্যবহারকারী যা তারা claim করে।
Authorization হল ব্যবহারকারী কোন রিসোর্স অ্যাক্সেস করতে পারে তা নির্ধারণ করার প্রসেস।

IAM কি করে?

আইডেন্টিটি এবং অ্যাক্সেস ম্যানেজমেন্ট আপনাকে ব্যবহারকারীর validation এবং resource অ্যাক্সেসের উপর নিয়ন্ত্রণ দেয়:

কিভাবে ব্যবহারকারীরা আপনার সিস্টেমের একটি অংশ হয়ে ওঠে
ব্যবহারকারীর কোন তথ্য সংরক্ষণ করতে হবে
কিভাবে ব্যবহারকারীরা তাদের আইডেন্টিটি প্রমাণ করতে পারেন
কখন এবং কত frequently ব্যবহারকারীদের তাদের পরিচয় authenticate করতে হবে
কোন ব্যাবহারকারী কোন রিসোর্স অ্যাকসেস করতে পারবে এবং কোন রিসোর্স পারবে না তা নির্ধারণ করা

Authentication এবং Authorization

Authentication এবং Authorization এই দুইটা টার্ম একজন ইউজারের কাছে কনফিউজিং মনে হয়। এইটা হওয়াটা খুবই স্বাভাবিক। কারণ, এই দুটিই একজন ইউজারের কাছে একই experience মনে হয় যখন সে কোনো সিস্টেম ব্যাবহার করে। তবে, এগুলি দুটি পৃথক প্রক্রিয়া: authentication ব্যবহারকারীর পরিচয় প্রমাণ করে,আর অন্যদিকে authorization নির্দিষ্ট রিসোর্সগুলিতে ব্যবহারকারীর অ্যাক্সেসকে grant করে বা deny করে।

আপনি একটি অফিস বিল্ডিংয়ের নিরাপত্তা ব্যবস্থা হিসাবে Authentication এবং Authorization এর কথা ভাবতে পারেন। ব্যবহারকারীরা হল সেই ব্যক্তি যারা বিল্ডিংয়ে প্রবেশ করতে চান। লোকেরা যে সম্পদগুলি অ্যাক্সেস করতে চায় সেগুলি হল বিল্ডিংয়ের area গুলি: মেঝে, কক্ষ এবং আরও অনেক কিছু৷

Authentication: আপনি যখন বিল্ডিংয়ে প্রবেশ করবেন, আপনাকে অবশ্যই আপনার ফটো আইডি ব্যাজটি নিরাপত্তারক্ষীকে দেখাতে হবে। প্রহরী ব্যাজের ছবির সাথে আপনার মুখের তুলনা করে।যদি তারা মিলে যায়, গার্ড আপনাকে দরজা দিয়ে বিল্ডিংয়ের বিভিন্ন এলাকায় প্রবেশ করার চেষ্টা করতে দেয়। আপনি কোন কক্ষে প্রবেশ করতে পারবেন তা গার্ড আপনাকে বলে না; তারা শুধুমাত্র প্রমাণ চায় যে আপনি নিজেকে যে লোক হিসেবে দাবি করেছেন, সে লোকটা আপনি কিনা। এটি হল authentication: ব্যবহারকারীর পরিচয় নিশ্চিত করা।

Authorization: এই scenario-তে, কল্পনা করুন যে আপনি যে কোম্পানিতে চাকরি করেন সেটি একটি বিল্ডিংয়ে অবস্থিত। সাথে আরও অনেকের কোম্পানীও আছে ঐ বিল্ডিংয়ে। বিল্ডিংয়ের লিফট এবং দরজাগুলিতে অ্যাক্সেসের জন্য কিছু key-sensors রয়েছে। আপনার ব্যাজের সিকিউরিটি-চিপ আপনাকে শুধুমাত্র প্রথম তলায় অ্যাক্সেস দেয়, যেটি আপনার কোম্পানির জন্য বরাদ্ধ। আপনি অন্য কোনো ফ্লোরে প্রবেশ করতে আপনার ব্যাজ সোয়াইপ করলে, আপনার অ্যাক্সেস ডিনাই করা হবে। ঠিক একইভাবে, আপনি আপনার অফিসে শুধুমাত্র আপনার ডেস্ক access করতে পারেন। কিন্তু আপনার সহকর্মীদের ডেস্ক আক্সেসে আপনার পারমিশন নেই। আবার, আপনি সরবরাহ রুম প্রবেশ করতে পারেন কিন্তু সার্ভার রুম না। এটিই হল Authorization: পরিচয়ের উপর ভিত্তি করে বিভিন্ন রিসোর্সগুলিতে অ্যাক্সেস প্রদান এবং অস্বীকার করা।

এখন authentication এবং authorization এর পার্থক্যগুলির একটা কুইক রিভিউ দেখে ফেলিঃ

সংক্ষেপে, একটি resource এর অ্যাক্সেস authentication এবং authorization উভয় দ্বারা protected। আপনি যদি আপনার পরিচয় প্রমাণ করতে না পারেন, তাহলে আপনাকে কোনো রিসোর্সে প্রবেশের অনুমতি দেওয়া হবে না। এবং এমনকি যদি আপনি আপনার পরিচয় প্রমাণ করতে পারেন, আপনি যদি সেই রিসোর্সের জন্য অনুমোদিত(authorized) না হন, তাহলেও আপনাকে অ্যাক্সেস থেকে বঞ্চিত করা হবে।

Support for password authentication was removed. Please use a personal access token instead.

Shafia Rahman Chowdhury — Tue, 04 Jul 2023 13:07:03 +0000

While pushing some codes into your GitHub repository you may encounter the error "Support for password authentication was removed. Please use a personal access token instead." as shown in the picture below

Starting from August 13, 2021, GitHub has stopped accepting passwords for verifying Git operations on user accounts. Instead, you will need to use a Personal Access Token (PAT) in place of your password. To add a PAT to your system, you can follow the steps outlined below.

Step 1: Go to your GitHub Account and then go to the Settings(click on your profile account and you will find the Settings option there)

Step 2: Scroll down and at the sidebar you will see the Developer Settings option. Click on Developer Settings.

Step 3: Click on Personal access tokens and then click on Tokens (classic)

Step 4: Click on Generate new token and then click on Generate new token (classic)

Step 5: Fill-up the Note field, select No expiration and then select the checkboxes as shown in the picture

Step 6: Click on the Generate token. Your token is created!.

Step 7: Copy the token and paste it on the password field of the terminal.

Your code got successfully pushed into your repository!

However, after applying your token you may face this error.

Visit this blog(https://dev.to/shafia/common-github-issues-beginners-may-face-29bb) and follow the steps given in Error 3 Solution 1.

Happy coding!

Solutions To Some Common GitHub issues

Shafia Rahman Chowdhury — Fri, 26 May 2023 13:28:50 +0000

Sometimes, you may come across various challenges when using GitHub. In this blog post, we will explore some common issues we encounter and provide practical solutions to help you overcome them. Let's dive in!

Error-1: Git Configuration error

Solution

Step 1: The image shows two commands in the terminal. If you receive these commands, execute them one by one in your terminal.

git config --global user.email "your github email"
git config --global user.name "your github name"

Step-2: A pop-up with sign in with browser will appear. Make sure you are logged in your GitHub Account. Click on the
sign in with browser and then click Authorize Visual Studio Code button

Step 3: Go to your terminal again and run these commands

git branch -M main
git remote add origin "your repo link"
git push -u origin main

Error-2: (e.g git pull...) before pushing again

Solution

If you're submitting your code to GitHub for the first time, open your terminal again and run these commands:

git push -u origin main -f

If you've already pushed your code to the GitHub repo more than once.

git push -f

Error-3 : src refspec main does not match any

Solution-1

Step 1: Go to GitHub Settings and then go to Emails

Step-2: Uncheck Keep my email addresses private

Step-3: Push your code again

Solution-2

Open your Git bash terminal and run the following commands one by one:

rm -rf .git
git init
git add .
git commit -m "added"
git branch -M main
git remote add origin <YOUR_GITHUB_REPO_LINK>
git push -u origin main -f

Error 4: Requested URL returned error: 403

This error takes place when you do not have access to a repository.

Solution-1

Step-1: Check if you are pushing the code to your repository

git remote -v

Step-2: Open a new repository in your GitHub

Step-3: Copy your repository link

Step-4: Go to the terminal and write the following command:

git remote set-url origin your-repo-link

After the entering command, check if the git repository url changed. Write git remote -v on your terminal.

Step-5: Then, run these commands one by one

git branch -M main
git push -u origin main

Solution-2

https://dev.to/shafia/requested-url-returned-error-403-1pfm

Follow the solutions discussed above and get rid off your errors.

Visit the link below and learn how to resolve the GitHub error "Support for password authentication was removed".

https://dev.to/shafia/support-for-password-authentication-was-removed-please-use-a-personal-access-token-instead-4nbk

Don't let these common issues discourage you. Keep exploring, collaborating, and contributing on GitHub, and watch your skills grow. Happy coding!

Troubleshooting Broken Image and CSS Issues on GitHub Pages

Shafia Rahman Chowdhury — Fri, 26 May 2023 12:47:12 +0000

Are you facing a situation where you have successfully deployed your webpage to GitHub Pages, but the images or your CSS code are not showing up after the deployment? Don't worry; this is a common issue that many people encounter.

There are two possible reasons for this error to take place:

1) Wrong name
2) Wrong path

1) Wrong Name

Always check the spelling of the image you saved and name of the css file.

If you save your image as first-image.jpg or your css code as style.css but you wrote in your path 'First-image.jpg' or 'Style.css', it will not be visible on GitHub Pages.

But why?

You won't see such problem in your localhost because the file system might not distinguish between uppercase and lowercase letters in file names but after deploying your site on GitHub you will encounter such problem as GitHub is case-sensitive.

2) Wrong Path

Always check if your image path and css file path are written correctly.

Since the solution for both issues is the same, I will provide examples related to images only.

Alright, now let's see how to access an image.

a) If you save your image in the root folder such as the one shown below

Note: The "root folder" is the main or starting folder for your project.

Then your image path will be:

<img src="header_bg.png" alt="header" />

b) If you save your image inside a folder you created such as the one shown below

Then you will have to access your image by following the pattern ./folder_name/image_name

For example:

<img src="./images/hardy.png" alt="apple" />

c) If you save your image inside a folder of a folder such as the one shown below

Then you will have to access your image by following the pattern
./folder_name/folder_name/image_name

For example:

<img src="./images/icon/developer.png" alt="apple" />

And so on...

However, if your html file is in one folder **and your images or css files are in **another folder

Then you will have to access your image by following the pattern
../folder_name/image_name

For example,

<img src="../images/hardy.png" alt="apple" />

Remember, same thing applies for the css file names.

Sometimes, we do not use the dots(../ or ./) and we will still be able to view the images on our localhost. However, when deploying the same code on GitHub Pages without using the dot notation, the images and css code might not be displayed.

But why?

When you're working on your computer (localhost), not using the dots (./ or ../) in file paths might still allow images and CSS to display because the computer assumes you mean files are in the current folder.

However, when you put the same code on GitHub Pages, it becomes more strict. Without using the dot notation, GitHub Pages might get confused about where to find the images and CSS because it follows specific rules. The dots help specify the file paths correctly, making sure GitHub Pages can locate and display them properly.

Summary

If you write your image path like the one shown below

Wrong
1) src="images/my-image.png"
2) url(images/my-image.png)
3) href="css/main.css"

your image and css code may not appear on GitHub Pages so, make sure to place ./ or ../ when deploying your site on GitHub Pages or any other hosting platform:

Right
1) src="./images/my-image.png" (if the html code is in root folder and the css code is another folder)

2) url("../images/my-image.png") (if the css code is in one folder and the image is in another folder)

3) href ="./css/main.css" (if the html code is in root folder and the css code is another folder)

4) href ="../css/main.css" (if the html code is in one folder and the css code is another folder)

Happy deploying!

Some Common Vercel Errors

Shafia Rahman Chowdhury — Mon, 15 May 2023 13:26:06 +0000

When deploying your server-side on Vercel, you may face some common errors sometime. In this blog, I will provide solutions to help you resolve these following errors effortlessly.

1) Error

Cannot GET/your_route_name

Solution

Step-1: Remove "await client.connect ()" in the try block of the run function of your index.js file

Step-2: Go to your vercel.json file and change your dest value to index.js like the one below:

{
   "version": 2,
   "builds": [
       {
           "src": "./index.js",
           "use": "@vercel/node"
       }
   ],
   "routes": [
       {
           "src": "/(.*)",
           "dest": "index.js"
       }
   ]
}

Step-3: Then, run these command on your terminal

vercel
vercel --prod

2) Error

This Serverless Function has crashed

This error have few possible solutions

Solution - 1

Step-1: Remove "await client. connect ()" in the try block of the run function of your index.js file

Step-2: Then, run these command on your terminal

vercel
Vercel --prod

Solution - 2

Step-1: Go to your index.js file, remove app.use(cors()) and write this code instead:

const corsConfig = {
    origin: '',
    credentials: true,
    methods: ['GET', 'POST', 'PUT', 'DELETE']
}
app.use(cors(corsConfig))
app.options("", cors(corsConfig))

Step-2: Then, go to your vercel.json file and copy-paste this code:


{
    "version": 2,
    "builds": [
        {
            "src": "./index.js",
            "use": "@vercel/node"
        }
    ],
    "routes": [
        {
            "src": "/(.*)",
            "dest": "/",
            "methods": ["GET", "POST", "PATCH", "DELETE", "OPTIONS"]
        }
    ]
}

Step - 3: Then, run these command on your terminal

vercel
Vercel --prod

_If you still see the error change dest value to "dest": "index.js" and deploy the server again using the step-3 command.

Solution-3

Check if you have added your environment variables in your Vercel

Go to Vercel dashboard --> Choose the project --> settings--> Environment Variables

Make sure the enviroment variables you added match with the one in your .env file

Solution-4

If any of the above solutions don’t work, then run this command on your terminal

vercel logs your_production_url

Vercel will let you know if there is any errors in your index.js file.

3) Error

bad credentials Vercel sign up

Step-1: Run this command on your terminal to uninstall Vercel

npm uninstall -g vercel

Step-2: Re-install Vercel globally

npm i -g vercel

Step-3: Now login using the command below:

vercel login

4) Error

This Serverless function has timed out

Visit this blog to resolve this issue:

https://dev.to/shafia/the-errors-you-may-face-for-not-whitelisting-the-ip-address-0000-in-your-mongodb-network-access-32f8

5) Error

Fix vercel error : A system error occurred: uv_os_gethostname returned ENOSYS (function not implemented)

If you are using Windows 7, you may face this error

Solution:

Step-1: Go to Users -->your_computer_name folder –>
node_modules->vercel->dist->index.js

Step-2: On the top write,

const os=require("os")
os.hostname=()=>"localhost"

Lastly, if you don’t know how to deploy your server using Vercel CLI, follow this blog

https://medium.com/@shafiarahmanchy13/how-to-deploy-a-node-express-server-using-vercel-cli-f0a464d4e88c

For each error, I have provided step-by-step solutions to help you resolve them effectively.

By following the steps outlined in this blog, you can troubleshoot and overcome these errors.

Happy deploying!

Analyzing and interpreting the BSONTypeError

Shafia Rahman Chowdhury — Wed, 10 May 2023 13:11:15 +0000

What does this error mean?

“BSONTypeError:Argument Passed In Must Be a String of 12 Bytes or a String of 24 Hex Characters or an Integer"

Before we dive into knowing what this error means and when it occurs let’s understand what BSON means.

BSON is like a binary version of JSON, a way to represent data. It is similar to JSON because it supports different data types like strings, numbers, Booleans, arrays, and objects. But BSON goes further by adding more types such as dates, binary data, and special types like ObjectID and Decimal128. This allows MongoDB to handle a wider range of data in a more efficient way.

Therefore, when we see the error “BSONTypeError” it means the data provided does not match the expected BSON (Binary JSON) type.

Now let us understand this error

“BSONTypeError: Argument Passed In Must Be a String of 12 Bytes or a String of 24 Hex Characters or an Integer”

You see this error message when the ID you provided is not 12 Bytes String, 24 Hex characters String or a number.

MongoDB uses something called an ObjectID to identify each document in a collection. An ObjectID is a special code made up of 12 bytes, usually shown as a string of 24 letters and numbers. So, when you work with ObjectIDs or perform queries that involve them, it's important to make sure that the ID you provide follows this specific format of 12 bytes or 24 characters in hexadecimal (letters and numbers).

If you try to save or use a value in MongoDB that is not supported or doesn't match what MongoDB expects, you may see a "BSONTypeError" error.

Here are some common situations that can cause this error:

1) Invalid Format: If the ID you provided has a string with fewer or more than 24 characters, or contains non-hexadecimal characters, MongoDB will raise this error.

Wrong:

2.Wrong Data Type: If the ID you provided is not one of three specific data types: 24 byte hex string, 12 byte binary string or a Number.

Wrong:

Correct Format:

In this example, validId represents a valid ID as it follows the following format:

1) It consists of 24 characters, which are all hexadecimal (0-9, A-F).

2) The ID is provided as a string

If you get this error, always check if the ID you have sent from the client-side follows the format discussed in the Correct format.