strip-ansi | Strip ANSI escape codes from a string | Runtime Evironment library

As has been commented in the comments section, the issue has been solved by moving the project folder outside the OneDrive directory.

Because it's a synchronized cloud folder, as soon as you install/add/delete/update anything, it's being updated in the OneDrive cloud so the file/folder it's being used in the background and potentially unreachable. If at this time you try to develop the project (gatsby develop or gatsby build) and the file is being used, you won't be able to run it.

I don't think it's a good practice to use a cloud folder because the amount of data synchronized (mainly because of the node_modules) it's something to care about (it's also ignored in the .gitignore for a reason) so moving it to any other folder outside the OneDrive directory should be enough to run your project because the rest of global dependencies, according to your logs, were successfully installed.

As the output states, it cannot automatically fix it:

Honestly, your best path is to choose not to worry about this. node-sass is presumably a development dependency, not something you are shipping to users. You're not going to accidentally manage to include a string that causes ansi-regex to run inefficiently. And even if you did, that's not going to take down your server. It's going to make your build pipeline take longer than you might like.

At the time of this writing, a clean install of node-sass (latest version is 6.0.1) with no other dependencies still results in the vulnerable ansi-regex being installed. So you'd have to engage in some special shenanigans to get things fixed. While those shenanigans may be worth it for something that installs a vulnerability on your production server, doing so in this case would probably mean applying a lot of effort to create a potentially-brittle fix for something that is a non-issue.

So I strongly recommend simply waiting for the next version of node-sass (which will be one of 6.0.2, 6.1.0, or 7.0.0) and hope that it has the issue fixed, and don't worry about it much if it doesn't.

The Vue 3 documentation has a Migration Build example. Follow their steps and maybe you'll find out where it went wrong.

Another solution might be to create the Vue 3 project from scratch, re-do the setups for router, store, vueconfig, etc, and then migrate your components and views one by one.

The documentation tries to be as clear as possible in the main differences between Vue 2 and Vue 3, so check the docs for a more precise explanation of it.

Replace start by create:

For official node.js MongoDB driver. The syntax for projection is like this

The problem was in

According to the documentation of webpack/webpack-dev-server you should run webpack serve instead of webpack-dev-server.

Try replacing in your package.json: