Unable to run application on ARM based MacOS devices

[adithyanotfound]

Describe the bug
Unable to run the application on ARM based MacOS devices.

To Reproduce
Steps to reproduce the behavior:

On a ARM based MacOS devices run:

1. npm install
2. npm run serve

Expected behavior

Actual behavior

Additional details

1. The application runs on the main branch which suggests that one of the recent PR has caused this issue.
2. Can be fixed by installing 2 packages @rollup/rollup-darwin-arm64 and @esbuild/darwin-arm64

System information
VS code version: Version: 1.94.2 (Universal)
OS version: Darwin arm64 23.0.0
Device: Macbook Air M2

[github-actions]

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

[DipanshuOjha]

Hi..
I would like to work on this issue

[pranshugupta54]

@DipanshuOjha, are you able to reproduce this?

It's working fine for me on Mac.

[DipanshuOjha]

@pranshugupta54 Yes I am able to reproduce this in my windows 11. Just waiting to get assigned so that I can put a pull request

[pranshugupta54]

@DipanshuOjha, the issue is about MacOS?

[DipanshuOjha]

@pranshugupta54
This issue envolves dockerising which will be helpful in both mac and windows

[pranshugupta54]

It's a separate thing, they are running it with npm run serve and not using docker. We have a different issue for docker.

@adithyanotfound, can you try deleting node_modules and then try again?

[DipanshuOjha]

@pranshugupta54 if you dockerise the application then their is no need to install the dependencies seperately it will be installed within node_modules.

[pranshugupta54]

@DipanshuOjha, we already have a separate project being done to fix the docker containers. But this is an issue with locally running it.

@adithyanotfound, to fix:
Please try npm i again after removing both package-lock.json and node_modules directory.

[adithyanotfound]

@pranshugupta54 That works but it is not ideal to completely change package-lock.json file. Also I found PR #2186 which removes a lot of lines from the package-lock.json file which has probably caused this issue. The application was working before that PR.