uwv wrote:

Delete the node modules folder then try ‘npm install’ again.

MagicCrayon9342 wrote:

in my experience, you absolutely MUST downgrade your npm version to v16.x in order to modify Scratch. (why does everyone let their code become so hard to work with?)

MagicCrayon9342 wrote:

in my experience, you absolutely MUST downgrade your npm version to v16.x in order to modify Scratch. (why does everyone let their code become so hard to work with?)

WojtekGame wrote:

MagicCrayon9342 wrote:

in my experience, you absolutely MUST downgrade your npm version to v16.x in order to modify Scratch. (why does everyone let their code become so hard to work with?)

imma get node 16.0.0 because it should get me the tools i need.

Node Documentation wrote:

Corepack is an experimental tool to help with managing versions of your package managers. It exposes binary proxies for each supported package manager that, when called, will identify whatever package manager is configured for the current project, transparently install it if needed, and finally run it without requiring explicit user interactions.

This feature simplifies two core workflows:

It eases new contributor onboarding, since they won't have to follow system-specific installation processes anymore just to have the package manager you want them to.

It allows you to ensure that everyone in your team will use exactly the package manager version you intend them to, without them having to manually synchronize it each time you need to make an update.

me@computername MSYS ~
$ corepack --help
━━━ Corepack - 0.14.2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  $ corepack <command>

━━━ General commands ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  corepack disable [--install-directory #0] ...
    Remove the Corepack shims from the install directory

  corepack enable [--install-directory #0] ...
    Add the Corepack shims to the install directories

  corepack hydrate [--activate] <fileName>
    Import a package manager into the cache

  corepack prepare [--activate] [--all] [--json] [-o,--output] ...
    Generate a package manager archive

You can also print more details about any of these commands by calling them with
the `-h,--help` flag right after the command name.

NVS readme wrote:

NVS is a cross-platform utility for switching between different versions and forks of Node.js. NVS is itself written in node JavaScript.

This tool is obviously inspired by other node version manager tools, especially nvm, from which it borrows a lot of ideas and some command-line syntax.

me@computername MSYS ~
$ nvs --help
NVS (Node Version Switcher) usage

nvs help <command>             Get detailed help for a command
nvs install                    Initialize your profile for using NVS
nvs --version                  Display the NVS tool version

nvs menu                       Launch an interactive menu

nvs add <version>              Download and extract a node version
nvs rm <version>               Remove a node version
nvs migrate <fromver> [tover]  Migrate global modules
nvs upgrade [fromver]          Upgrade to latest patch of major version

nvs use [version]              (Not available, source nvs.sh instead)
nvs auto [on/off]              (Not available, source nvs.sh instead)
nvs run <ver> <js> [args...]   Run a script using a node version
nvs exec <ver> <exe> [args...] Run an executable using a node version
nvs which [version]            Show the path to a node version binary

nvs ls [filter]                List local node versions
nvs ls-remote [filter]         List node versions available to download
nvs outdated                   List local node versions and available updates

nvs link [version]             Link a version as the default
nvs unlink [version]           Remove links to a default version

nvs alias [name] [value]       Set or recall aliases for versions
nvs remote [name] [uri]        Set or recall download base URIs

A version string consists of a semantic version number or version label
("lts" or "latest"), optionally preceeded by a remote name, optionally
followed by an architecture, separated by slashes.
Examples: "lts", "4.6.0", "6.3.1/x86", "node/6.7.0/x64"
Aliases may also be used anywhere in place of a version string.

ZZC12345 wrote:

WojtekGame wrote:

MagicCrayon9342 wrote:

in my experience, you absolutely MUST downgrade your npm version to v16.x in order to modify Scratch. (why does everyone let their code become so hard to work with?)

imma get node 16.0.0 because it should get me the tools i need.

Just use Corepack and NVS/NVM.
Corepack:

Node Documentation wrote:

Corepack is an experimental tool to help with managing versions of your package managers. It exposes binary proxies for each supported package manager that, when called, will identify whatever package manager is configured for the current project, transparently install it if needed, and finally run it without requiring explicit user interactions.

This feature simplifies two core workflows:

It eases new contributor onboarding, since they won't have to follow system-specific installation processes anymore just to have the package manager you want them to.

It allows you to ensure that everyone in your team will use exactly the package manager version you intend them to, without them having to manually synchronize it each time you need to make an update.

me@computername MSYS ~
$ corepack --help
━━━ Corepack - 0.14.2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  $ corepack <command>

━━━ General commands ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  corepack disable [--install-directory #0] ...
    Remove the Corepack shims from the install directory

  corepack enable [--install-directory #0] ...
    Add the Corepack shims to the install directories

  corepack hydrate [--activate] <fileName>
    Import a package manager into the cache

  corepack prepare [--activate] [--all] [--json] [-o,--output] ...
    Generate a package manager archive

You can also print more details about any of these commands by calling them with
the `-h,--help` flag right after the command name.

NVS:

NVS readme wrote:

NVS is a cross-platform utility for switching between different versions and forks of Node.js. NVS is itself written in node JavaScript.

This tool is obviously inspired by other node version manager tools, especially nvm, from which it borrows a lot of ideas and some command-line syntax.

me@computername MSYS ~
$ nvs --help
NVS (Node Version Switcher) usage

nvs help <command>             Get detailed help for a command
nvs install                    Initialize your profile for using NVS
nvs --version                  Display the NVS tool version

nvs menu                       Launch an interactive menu

nvs add <version>              Download and extract a node version
nvs rm <version>               Remove a node version
nvs migrate <fromver> [tover]  Migrate global modules
nvs upgrade [fromver]          Upgrade to latest patch of major version

nvs use [version]              (Not available, source nvs.sh instead)
nvs auto [on/off]              (Not available, source nvs.sh instead)
nvs run <ver> <js> [args...]   Run a script using a node version
nvs exec <ver> <exe> [args...] Run an executable using a node version
nvs which [version]            Show the path to a node version binary

nvs ls [filter]                List local node versions
nvs ls-remote [filter]         List node versions available to download
nvs outdated                   List local node versions and available updates

nvs link [version]             Link a version as the default
nvs unlink [version]           Remove links to a default version

nvs alias [name] [value]       Set or recall aliases for versions
nvs remote [name] [uri]        Set or recall download base URIs

A version string consists of a semantic version number or version label
("lts" or "latest"), optionally preceeded by a remote name, optionally
followed by an architecture, separated by slashes.
Examples: "lts", "4.6.0", "6.3.1/x86", "node/6.7.0/x64"
Aliases may also be used anywhere in place of a version string.

You don't have to uninstall the newer Node. I run Node experimental and stable on the same machine and manage pnpm via Corepack.