Forem: Ifeanyi Chima

Breaking web apps

Ifeanyi Chima — Thu, 23 Apr 2026 21:41:59 +0000

Introduction

THOR (The Hand Book of Open-source Repositories) is a website that provides world-class guidance on open-source contributions. This is very near and dear to my heart. Ever since I was 18 years old in 2019, I watched my friend get selected for G-soc. I struggled to understand how to go about it and I was always wishing I had a medium that would provide a very clear understanding of how to go about open-source. This buggled my mind for 7 years, until I finally sat down to build a website to help other people in the future that would want to understand open-source and how to go about it.

Project setup

I already had Nodejs installed on my computer, which is really all you need to use playwright and passmark. We were provided API keys through the mail, keep the API KEY safe inside your env (add .env to .gitignore)

OPENROUTER_API_KEY=sk-or-v1-your-actual-key-here

In three easy steps, you can setup your project.

You run this command. It will create a new folder called my-hackathon-tests with everything Playwright needs:

npm init playwright@latest my-hackathon-tests

Answer the prompts.

Move into your project folder

cd my-hackathon-tests

Install passmark and dotenv

npm install passmark dotenv

Here is a look at my folder structure, I have three test files in my project.

MY-HACKATHON-TESTS/
├── .sixth/
├── node_modules/
├── test-results/
├── tests/
│   ├── 01-homepage.spec.js
│   ├── 02-guest-flow.spec.js
│   └── 03-navbar.spec.js
├── .env
├── .gitignore
├── package-lock.json
├── package.json
└── playwright.config.js

Testing strategy

Writing tests in passmark is as easy as ABC literally, you write your descriptions in plain english sentences and the AI tries to understand it and do it for you. Although, the shortcoming in passmark is that the AI takes screenshots of your website and makes it's assertions which can burn through credits / tokens.

In my website, I had a flow that was repetitive, essentially, the user lands on the homepage and clicks a button to be taken to the dashboard, I did not want to keep repeating myself writing descriptions and assertions for that flow, so I created a helper function called navigateAsGuest

Now, here is where the shortcomings of passmark comes in because it takes screenshots of your website, repeating this flow of the user landing on the homepage and clicking a button can burn through credit / token very fast, so I landed on a split-mechanism approach, where I used playwright for navigation steps and only used passmark to make assertions. This was done because playwright has direct access to the DOM and can do DOM manipulations which saves on compute credit.

What I Tested

Homepage test: This test was done in a a build-driven development testing strategy because I am the main / lead developer of the website, I know what will be seen on the landing page (a logo, a "continue as guest" button, a large banner image) so I tested for the presence of these using a mixture of playwright and passmark, but I will not advice anyone to do it this way because in tech, we should follow a test-driven development style.

// 01-homepage.spec.js
test("Homepage loads with key elements", async ({ page }) => {
  test.setTimeout(120_000); // give it 2 minutes total

  await page.goto("https://ifeanyi-thor.netlify.app/");
  await page.waitForSelector("text=THOR"); // wait for specific text, not networkidle

  await runSteps({
    page,
    userFlow: "Verify homepage elements",
    steps: [],
    assertions: [
      { assertion: "The heading 'THOR' is visible on the page" },
      { assertion: "The subtitle 'The Handbook of Open-source Repositories.' is visible on the page" },
      { assertion: "There is a hammer/logo icon image visible on the page" },
      { assertion: "There is a large illustrated image of an astronaut cat visible on the left side" },
    ],
    test,
    expect,
  });
});

Guest flow test: This is a tricky test because you have to test for edge cases and user pattern is weird and hard to imagine, but here we are testing for when a user enters the website without authenticating with GitHub, we check that they are not able to use the following features: leave a comment, the markdown playground, but they can still use the sidebar to navigate throughout the documentation.

// 02-guest-flow.spec.js
test("Sidebar link 'introduction' loads the correct page", async ({ page }) => {
  test.setTimeout(60_000);
  await navigateAsGuest(page);
  await page.getByText("introduction").click();
  await page.waitForLoadState("networkidle"); // wait for content

  await runSteps({
    page,
    userFlow: "Verify introduction page content",
    steps: [],
    assertions: [
      { assertion: "The main content area shows the Introduction page content" },
    ],
    test,
    expect,
  });
});

Nav bar test: Here, I checked if the navigation links worked by correctly taking a user to the page they are meant to go to. The dark mode toggle button Oh my Gosh, this stressed me the most because I was trying to test that the dark / light mode toggle button works. So I ended up having to directly manipulate the DOM in the test instead of fighting the button.

// 03-navbar.spec.js
test("Playground nav link shows Authentication Required modal", async ({ page }) => {
  test.setTimeout(60_000);
  await navigateAsGuest(page);
  await page.getByRole("link", { name: "Playground" }).click();
  await page.waitForSelector("text=Authentication Required", { timeout: 10000 });

  await runSteps({
    page,
    userFlow: "Verify auth modal",
    steps: [],
    assertions: [
      { assertion: "A modal is visible on the page" },
      { assertion: "The modal contains the heading 'Authentication Required'" },
      { assertion: "The modal contains the text 'Please sign in with GitHub to use this feature'" },
      { assertion: "A 'Sign in with GitHub' button is visible inside the modal" },
    ],
    test,
    expect,
  });
});

We have three test files, with a single command we can run them

npx playwright test --project chromium

What I learned

Run tests sequentially

Without this, Playwright runs tests in parallel by default which caused our tests to interfere with each other.

// playwright.config.js
export default defineConfig({
  workers: 1,
})

Use passmark only for assertions

// wrong — costs credits just to click a link
steps: [{ description: "Click the Docs link" }]

// right — let Playwright click, let Passmark only assess
steps: []

Direct DOM manipulation when the UI fights you

// when clicking the actual button is unreliable
await page.evaluate(() => {
  document.documentElement.setAttribute("data-theme", "dark");
  localStorage.setItem("theme", "dark");
});

waitForLoadState("networkidle")

// waits for ALL network requests to finish
await page.waitForLoadState("networkidle");

Results


## Test Results

All 12 tests passed successfully across 3 test files in 3.1 minutes.

**12 passed — 0 failed — Total time: 3.1 minutes**

Resources

Github: https://github.com/MasterIfeanyi/thor-passmark-tests

THOR: https://ifeanyi-thor.netlify.app

Conclusion

I have written unit tests before this hackathon but it was a long time ago back in 2022 and this is the first time since 2022 that I am writing unit tests again. Oh, this really reminded me of how much I have missed it. This was the first time I saw that I can create multiple test files and they would all still run in parallel or sequentially. Seven years ago I watched my friend get into GSoC and had no roadmap to follow. I built THOR so nobody else has to feel that way. This hackathon pushed me to do something I hadn't done since 2022, write tests and it reminded me that shipping a product is only half the job. The other half is proving it works. Passmark made that second half genuinely enjoyable. If you have built something you care about, test it. Future you will be grateful.

Outreachy May, 2026

Ifeanyi Chima — Thu, 16 Apr 2026 00:20:49 +0000

Alright, let me start by saying: "Thank you universe", this is because I literally forgot that the initial applications for contribution phase for May-August, 2026 Outreachy internship had already started.

Initial Applications

It opened Feb 6 - Feb 13, 2026. I was only reminded by a random tweet from a stranger on the 11th hour (Feb 13, 2 pm). Applications closed by (Feb 13, 5 pm).

I have been singing about open-source to my friends for about some time now. I write articles about it. I have done hacktoberfest (twice in 2022 & 2023). It has always been on my mind to take on the big 3 - MLH, Outreachy and G-Soc

I need a job

My life is literally this meme and the best way to get a job is to have some experience under your belt, which the Outreachy internship will provide.

Interlude

Once you get selected after the initial applications, you would see different organisations, select the one that suits you best. I chose Mozilla firefox because it required knowledge of HTML, CSS, and JavaScript.

Contribution phase

Before you get selected as an intern with Outreachy, you need to take part in the contribution phase which lasts for about three (3) weeks. It actually ends today (March 20 - April 15, 2026).

I learned quickly how to use bugzilla to find issues on my own (I made sure to look out for bugs with the label good-first-issue) and how to create patches using phabricator. Bugzilla and Phabricator those words sound big and fancy but phrabicator is just a single line of code - moz-phab submit --single.

here is a sequence:

git checkout -b bug-2022414-array-profiles

git add "file name"

git commit -m "fix: migrations for profiles with backup enabled"

moz-phab submit --single

You submit a patch for a bug, you get feedback or review from a mentor and then you push again.

One thing I learned, always make sure that you checkout -b into a new branch from main so that the branch does not have unrealated histroy from other bugs or commits.

Final Application

In your final application, you would be asked a few questions, you are to write essays answering them, they ask about your experience with the organisation. Also, You need submit a timeline of the work you propose to do during the thirteen week internship. You look at the goal of the organisation and you outline how you intend to approach the task.

Thank you, please follow me.

This blog is only a single part, in a multi-series blog that I will write about my experience !!!!!!!!!

stay tuned.

Useless project.

Ifeanyi Chima — Mon, 06 Apr 2026 13:42:06 +0000

This is a submission for the DEV April Fools Challenge

What I Built

A button. Just a button.

You click it, and lines start crawling across your screen. 50 vertical lines and 50 horizontal lines slowly forming a grid of boxes like graph paper possessed by a ghost. That's it. That's the whole app. No data. No purpose. No redemption arc.

You can control how many lines appear, how fast they draw, and what color they are. You can also clear the grid and do it all over again, because apparently that's how you want to spend your time.

Demo

Code

MasterIfeanyi / grid-lines

How I Built It

Built with pure HTML5 Canvas, vanilla JavaScript, and zero regrets.

The core idea is simple, the canvas is just a blank piece of paper. I grab a "pencil" using getContext('2d'), pre-calculate all the x and y positions for each line by dividing the canvas width and height by the number of lines, store them in two arrays (verticals[] and horizontals[]), then draw them one by one using setTimeout so you can actually watch the chaos unfold in real time.

No frameworks. No libraries. No npm install. Just a canvas, a loop, and a questionable life decision.

Prize Category

Community Favorite.

Two worlds of mine colliding !

Ifeanyi Chima — Wed, 18 Feb 2026 17:30:37 +0000

Ben Halpern for The DEV Team

Feb 18

A New Chapter: DEV is Joining Forces with Major League Hacking (MLH)

#news #devto #hackathon #discuss

386

Comments 106

6 min read

A must read on how to implement GitHub actions.

Ifeanyi Chima — Sun, 18 Jan 2026 10:55:01 +0000

Ifeanyi Chima

Mar 18 '24

GitHub actions example

#javascript #webdev #devops #githubactions

Comments

2 min read

Demistifying Nextjs

Ifeanyi Chima — Sun, 18 Jan 2026 09:17:22 +0000

2026, Happy new year

It's been a while, my dear. I have been learning Nextjs by building an open-source project that is available for everyone to contribute at THOR.

In this article, I will try to demystify Nextjs

first, let's lay some ground work or establish some fundamentals.

Client vs Server

In Nextjs, you can have 2 types of components, namely (server) and (client) components. The server components will never run in the browser and they can be used to make calls to the backend or even directly to a DB. The client components can and will run in the browser, where you have access to localStorage and browser window, it is advisable to not have things such as API keys and secrets in the client components. To make a page a client component, you do this "use client".

File based routing

In Nextjs, you have "file-based routing" which means once a folder or file is created in /src/app directory it becomes a route that can be reached. example if I wanted a "community" route, I would create this /src/app/community/page.js. This will become a route that you can navigate to. Remember to add "use client", if you want the component to be a client component.

_components

In Nextjs, if you do not want certain components / pages that you create to become routes that can be accessed i.e You want to create components such as ToggleButton.jsx, Sidebar.jsx, NavbarLayout.jsx, Avatar.jsx etc. all of these are components that can be reused but I don't want them to become "routes", you can create a folder like this _components and every component you create inside that folder will never be route.

Fetch API

In Nextjs, if you want to make requests that involves API_KEYS or SECRETS to the backend or database, it is advisable to do that from a server component, and gone are the days of getServerSideProps, getStaticParams, and getStaticProps. now you can just use the native fetch API in Javascript to make those requests and you can mimic those behaviours using


const data = await fetch('https://api.example.com/data', {...options})

Here are some options.

Want fresh data every time? → cache: 'no-store' - this used to be getServerSideProps

Want cached data? → cache: "force-cache" - default behavior, similar to getStaticProps

Want periodic revalidation? → next: { revalidate: seconds } - this used to be getStaticProps with revalidate (ISR)

These 3 used to scare me so much, gosh !!!

route group

In Nextjs, if you have a bunch of files or folders and you want to group them for organization and readability, you can create a folder like this (docs) which will contain all of them to keep your workspace neat. e.g src/app/(docs)/content/page.js. This way you have many files in one place.

Thank you, Please follow me

Twitter

Navbar scroll event

Ifeanyi Chima — Sat, 19 Jul 2025 10:09:31 +0000

Today, I want to show you how I darken the navbar when a user scrolls on the website.

THE SECRET

I am using an event listener scroll which I attached to the navbar to listen for when the user scrolls beyond a certain screen size. This will allow the text on the navbar to be readable.

Using JavaScript, we add two classes to the navbar

bg-dark: this will give the navbar a dark background. I believe this is an in-built bootstrap class.
slow: this will add animation to make the navbar slowly darken.

HTML

<!--NavBar-->
<nav class="navbar navbar-dark py-3 navbar-expand-lg fixed-top">
    <div class="container">
        <a href="#" class="navbar-brand">
            <img src="./img/halo-logo.jpg" class="img-fluid logo" alt="">
        </a>

        <button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navmenu">
            <span class="navbar-toggler-icon"></span>
        </button>

        <div class="collapse navbar-collapse" id="navmenu">
            <ul class="navbar-nav me-auto">
                <li class="nav-item">
                    <a href="#home" class="nav-link active">GAMES</a>
                </li>
                <li class="nav-item">
                    <a href="#news" class="nav-link">NEWS</a>
                </li>
                <li class="nav-item">
                    <a href="#about" class="nav-link">ESPORTS</a>
                </li>
                <li class="nav-item">
                    <a href="#occupation" class="nav-link">COMMUNITY</a>
                </li>
                <li class="nav-item">
                    <a href="#occupation" class="nav-link linkarrow">SUPPORT<i class="ri-arrow-right-up-line"></i></a>
                </li>
                <li class="nav-item">
                    <a href="#occupation" class="nav-link linkarrow">GEAR<i class="ri-arrow-right-up-line"></i></a>
                </li>
            </ul>
            <a href="#footer" class="btn btn-brand">GET HALO</a>
        </div>
    </div>
</nav>

CSS


.slow{
    @include transition-ease;
}

@mixin transition-ease{
    transition: all 1.4s ease;
}

JavaScript


const nav = document.querySelector("nav");

window.addEventListener("scroll", () => {
    if (window.scrollY > 100) {
        nav.classList.add("bg-dark", "slow")
    } else {
        nav.classList.remove("bg-dark", "slow")
    }
})

Explaination

we capture the navbar using DOM manipulation.
we add an event listener to the browser window to listen for when a user scrolls beyond 100 vh.
we add the classes "bg-dark" and "slow" to the navbar.

Thank You, Please Follow me.

Firebase: My negative Experience

Ifeanyi Chima — Sat, 05 Jul 2025 21:56:43 +0000

I am working on a website that will allow a user to login and upload images to his website through a dashboard.

Problem 1

The first issue that I ran into was firebase SDK. I could not use npm packages directly in HTML/CSS. I had to use firebase SDK like this:


import { initializeApp } from "https://www.gstatic.com/firebasejs/11.8.1/firebase-app.js";
import {getAuth, onAuthStateChanged } from "https://www.gstatic.com/firebasejs/11.8.1/firebase-auth.js";

Here is a Fix:

Upgrade Firebase SDK - Make sure you're using the latest versions:

npm install firebase@latest

Problem 2


const firebaseConfig = {
    // authDomain: "oleru-young.firebaseapp.com",
    // storageBucket: "oleru-young.firebasestorage.app",
};

After enabling Storage, you'll see the bucket name in the Firebase Console. It will look like one of these:

oleru-young.appspot.com (older format)
oleru-young.firebasestorage.app (newer format)

This caused a lot of confusion, if you were wondering the newer format is the correct thing to follow.

Problem 3

CORS - I had to battle with this error


Access to XMLHttpRequest at 'https://firebasestorage.googleapis.com/v0/b/oleru-young.appspot.com/o?name=uploads%2F11f20756a8694b63b7ee0645cde15e2e.jpg' from origin 'http://127.0.0.1:5500' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.

means your browser is blocking the request to Firebase Storage due to a CORS (Cross-Origin Resource Sharing) issue. Here’s how to fix it.

Here is a fix

Step 1:

Create a cors.json file in your VScode project and add the following syntax

[
  {
    "origin": ["*"],
    "method": ["GET", "POST", "PUT", "DELETE", "OPTIONS"],
    "maxAgeSeconds": 3600,
    "responseHeader": ["Content-Type", "Authorization"]
  }
]

Step 2:

Using your terminal in VScode, you need to login to google cloud by using the terminal

gcloud auth login

If you're working on a project and want to set the active project after logging in, you can run:

gcloud config set project [PROJECT_ID]

Replace [PROJECT_ID] with your actual Google Cloud project ID.

CORS

Set the CORS policy for your project by running this


gcloud storage buckets update gs://[PROJECT_ID].firebasestorage.app --cors-file=cors.json

Problem 4

Firebase Storage Rules

You need to set the rules for the bucket. When you are creating the bucket for the first time. You need to choose test mode. This will allow read and write access to the bucket for up to 30 days.

A firebase bucket looks like this.

rules_version = '2';


service firebase.storage {
  match /b/{bucket}/o {
    match /{allPaths=**} {
      allow read, write: if true;
    }
  }
}

Use something permissive for testing (not production-safe):

Google Cloud Auth Issue

Ifeanyi Chima — Sun, 01 Jun 2025 12:10:16 +0000

Copying file://kitten.png [Content-Type=image/png]... ServiceException: 401 Anonymous caller does not have storage.objects.create access to the Google Cloud Storage object. Permission 'storage.objects.create' denied on resource (or it may not exist).

Steps to recreate it.

Having this issue while trying to copy a file to a new cloud storage bucket.

Download a cat image This will download the image for us.

wget https://cloud.google.com/storage/images/kitten.png

Try to copy the image to my cloud storage bucket

gsutil cp kitten.png gs://gcp-ifeanyi-tutorial

Now, we run into the issue stated above.

Steps to Resolve

gcloud auth login

Open your terminal and login to google cloud
Follow the prompt (Type Y for yes)
Copy the link provided in your browser
Select your google account and grant permission

After following the prompt you will be provided with a key that looks like this
4/9ANIR-c9k6BnlT ..........

Copy the key and paste it in your google cloud console
Try to run the previous command again

gsutil cp kitten.png gs://gcp-ifeanyi-tutorial

Load-balancing using docker and nginx

Ifeanyi Chima — Mon, 17 Mar 2025 16:07:07 +0000

Let me be clear this article is not a tutorial on NGINX or Docker. Just how to setup Load-balancing using both (Nginx and Docker). I will be assuming pre-requiste knowledge of both subjects.

In this article, we will be looking at how to achieve load-balancing using nginx and docker. well, what exactly is nginx and what is docker ?

Understanding Load-balancing - A website can have millions of requests, which can cause a bottleneck and make the latency (response time) slow. We need a way to handle the millions of request, to do this we need to increase the number of servers.

NGINX

Nginx - is a web server that serves us web content.

Nginx can forward a user request to an available server. This is called (load balancing). Nginx chooses which server will handle user request at each time.

nginx.conf - the file to setup nginx


http {

upstream backendserver {
        # here, we can specify all the backend url, that we have.

        server 127.0.0.1:9000;
        server 127.0.0.1:9001;
        server 127.0.0.1:9002;
    }

server {
listen 8080;

location / {
            proxy_pass http://backendserver/;
        }

}

}

cd nginx - nginx

To start the nginx server

Docker

Docker - is a way to package your application, as a developer. This way another developer can quickly setup same application on their system without running into a lot of issues and errors along the way. A dockerfile comes with all of the necessary instructions needed to setup said application.

Now, Docker can host a nodejs web-server inside of a container for you, this way we can run multiple servers at once, just by spinning up multiple instances of docker containers.

I ran into a major problem when using dockerfile to spin up my containers.

Problem 1

The index.js file has changed, do I need to rebuild the dockerfile and if I do that, would I need to re-create new containers based off on the new docker image

Answer

The answer to that question was Yes, if the index.js file has changed, you need to rebuild the Docker image to include the updated code. After rebuilding the Docker image, you will need to recreate the containers based on the new image to run the updated code.

Doing this everytime feels repetitive and tiring.

Problem 2

Is there a way to automatically restarting your container every time a file has changed without the need to rebuild your image each time ?

Answer

The answer to that question was Yes, we have two ways or options to do that

Docker Compose
Mount Volumes

I would be looking into the second option for today, you can use Docker volumes to mount your local directory into the container. This way, any changes you make to your local files will be reflected in the running container without needing to rebuild the image.

So, we need a dockerfile that would contain information about the web-server.

# Uses node version 16 as our base image
FROM node:16

# Create app directory inside the docker image
WORKDIR /usr/src/app

# Copy package.json into the app directory of the docker image
COPY package.json ./

# Install dependencies
RUN npm install

# Copy our entire code into the app directory of the docker image
COPY . .


# Install nodemon globally
RUN npm install -g nodemon

# expose port
EXPOSE 3000

# Run app
CMD ["nodemon", "--legacy-watch", "index.js"]

I need to explain the dockerfile a bit

# Run app
CMD ["nodemon", "--legacy-watch", "index.js"]

This will ensure that nodemon automatically restarts the container when we make changes to our nodejs code locally.

Now, we can carry on.

Build the Docker image:

 docker build -t node-application .

Run the container with a volume mount:

We would have two docker containers running, so we would run this command twice.

(-e CONTAINER_NAME=web1): This is the environment variable to help us distinguish between each container.
(--name web1): This is the name of the container.
(-p 9001:3000): This is port-mapping, we expose the container's port (3000) to our local computer port (9000).

docker run -d -p 9001:3000 --name web1 -v C:\Users\PC\Documents\Documents\2025\nginx_tuts\server:/usr/src/app -e CONTAINER_NAME=web1 node-application

Nodejs

const express = require("express");

const app = express();

app.get("/", (req, res) => {
  console.log(`say nigga ${process.env.CONTAINER_NAME} hit`);
  res.send(`Hello World from ${process.env.CONTAINER_NAME}`);
});


app.listen(3000, () => {
  console.log("Server is running on port 3000");
});

This is how my basic nodejs-express server was setup

Thank you, please follow me

How to connect Git to GitHub

Ifeanyi Chima — Thu, 20 Feb 2025 21:47:43 +0000

I bought a new laptop and I need to configure it properly. In this series, I will guide you, so that you can use if for programming.

In this article, I will guide you on how to install Git bash (adding a user account) and how to connect to GitHub so that you can upload (push) to your cloud GitHub Repo

1. Installing Git Bash:
Go to the official Git website: https://git-scm.com/downloads

2. Setting up a user account in Git:
After installation, open Git Bash and set up your user account with the following commands:

git config --global user.name "Barack Obama"
git config --global user.email "barack@gmail.com"

3. Connecting to GitHub:

Generate an SSH key (if you don't already have one):

ssh-keygen -t ed25519 -C "barack@gmail.com"

Press Enter to accept the default file location. You can choose to set a password or leave it empty. Now, you can start the SSH agent:

eval "$(ssh-agent -s)"

Add your SSH key to the agent:

ssh-add ~/.ssh/id_ed25519

run the following command and then copy the output, this is your public SSH key

cat ~/.ssh/id_ed25519.pub

Add the SSH key to your GitHub account:

Go to GitHub.com and sign in
Click on your profile picture in the top right and select "Settings"
In the left sidebar, click on "SSH and GPG keys"
Click "New SSH key"
Give your key a title (e.g., "My New Laptop")
Paste your public key into the "Key" field
Click "Add SSH key"

Hopefully, after following the steps stated above, you have successfully linked your computer to GitHub. To test this out, run a git clone command to clone a GitHub repository.

Clone your repository
If you do not have any repository, please feel free to clone mine.

git clone git@github.com:MasterIfeanyi/ifeanyi-coinnest-html.git

Summary

Now you should be all set up with Git Bash, connected to GitHub.

Thank you, please follow me

How to set execution policy for npm start

Ifeanyi Chima — Wed, 19 Feb 2025 15:28:19 +0000

I bought a new laptop and I need to configure it properly. In this series, I will guide you, so that you can use if for programming.

I got an error when I tried to run npm start

This error was thrown because I had not enabled running of scripts by the computer.

Here is a step-by-step guide to enable running of scripts.

To set the execution policy for npm start in PowerShell, you need to adjust the PowerShell execution policy to allow scripts to run. Here's how:

1. Open PowerShell as Administrator:

Press Win + X and select Windows PowerShell (Admin).

2. Check the Current Execution Policy:

Type the following command and press Enter:

Get-ExecutionPolicy

If the result is Restricted, it means script execution is disabled.

3. Set the Execution Policy:

To allow local scripts to run and require downloaded scripts to be signed, use the following command:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Type Y and press Enter to confirm the change.

4. Verify the New Execution Policy:

Run Get-ExecutionPolicy again to ensure the policy is set to RemoteSigned.

5 Now you should be able to run npm start without encountering the execution policy error.