v8.dev | source code of v8.dev , the official website | Web Site library

To fix node-sass issue, change "node-sass": "xx.xx.x" to "sass": "^1.49.0" in the package.json file in the root of the project. Then run npm i to install new packages.

Though node-sass may be not the only issue with ngx-admin to make it run nowadays.

I had the same problem. I got it working after I used chromedriver version 87.0.1 or higher.

import sys; print "%s.%s.%s"

That's some good old Python 2 notation if I ever saw some :)

As @ElapsedSoul mentioned. macOS 12.3 removed the Python 2 that came by default for all these years. Therefore, I would personally recommend for others not to upgrade to 12.3 if you need Python 2 until you find an alternative solution.

Some possible alternatives include the following:

Homebrew unfortunately got rid of Python 2 a long time ago. There are however some workarounds to try and get it to work: How to reinstall python@2 from Homebrew?.

I haven't tested this, so it might not work. But if it does, this is likely the best solution for your needs. From the following:

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.

these deprecations are related to the libraries version that are used directly by serverless. You can expect them to sooner or later be addressed on that library level but until that, you can use it without worries (unless you see the explicit security warnings, but that's not the case at the moment).

Try:

There are 2 ways to fix this problem.

1. It seems that you are importing modules to some js files but not using them so avoid using unnecessary imports and only import a module when you are using it on the page. If you are not using it then avoid importing that module to the js file.

1. Install the following module npm install --save-dev eslint-plugin-react. (for developers using NPM) or yarn add --dev eslint-plugin-react. (for developers using Yarn)

   Then, in your .eslintrc.json, under extends, include the following plugin:

In my case upgrading the node version solved the issue.

As you are using node version 17, I can see that this problem happens,

Downgrading to node version 16 will solve the problem(using nvm):