Ошибка npm is not defined

[18:18:32] Requiring external module babel-register
fs.js:27
const { Math, Object, Reflect } = primordials;
                                  ^

ReferenceError: primordials is not defined

npm -g install gulp-cli

Ответы:

{
  "dependencies": {
    "graceful-fs": {
      "version": "4.2.3"
    }
  }
}

{
  // Your current package.json contents
  "resolutions": {
    "graceful-fs": "4.2.3"
  }
}

{
  // Your current package.json
  "scripts": {
    // Your current package.json scripts
    "preinstall": "npx npm-force-resolutions"
  },
  "resolutions": {
    "graceful-fs": "4.2.3"
  }
}

npm install -g n

sudo n 11.15.0

    {
      "dependencies": {
        "graceful-fs": {
            "version": "4.2.2"
         }
      }
    }

npm install -g n

sudo n 11.15.0

npm install gulp@^3.9.1
npm install 
npm rebuild node-sass

ReferenceError: primordials is not defined in node

$ cd /to/your/project/
$ nvm install lts/dubnium
$ nvm use lts/dubnium
$ yarn upgrade # or `npm install`

nvm install 11.15.0

nvm use 11.15.0 #just in case it didn't automatically select the 11.15.0 as the main node.

nvm uninstall 13.1.0

npm rebuild node-sass

 "engines": {
    "node": "10.15.3",
    "npm": "6.9.0"
 }

n 10.16.0

nvm install 10.16.0

npm i -g npm-check-updates
ncu -u
npm install

gulp.task(
    'sass', function () {
        return gulp.src([sourcePath + '/sass/**/*.scss', "!" + sourcePath + "/sass/**/_*.scss"])

            ....

    }
);

Other config...

gulp.task(
    'watch', function () {
        gulp.watch(sourcePath + '/sass/**/*.scss', ['sass']);
    }
);

gulp.task('sass', gulp.series(function(done) {
    return gulp.src([sourcePath + '/sass/**/*.scss', "!" + sourcePath + "/sass/**/_*.scss"])

            ...

    done();
}));

Other config...

gulp.task(
    'watch', function () {
        gulp.watch(sourcePath + '/sass/**/*.scss', gulp.series('sass'));
    }
);

npm ERR! node v12.4.0
npm ERR! npm  v3.3.12

npm ERR! primordials is not defined
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:

{
  "dependencies": {
    "graceful-fs": {
        "version": "4.2.2"
     }
  }
}

"scripts": {
    "preshrinkwrap": "git checkout -- npm-shrinkwrap.json",
    "postshrinkwrap": "git checkout -- npm-shrinkwrap.json"
}

npm i gulp-cli -g

"dependencies": {
  "gulp": "^4.0.0"
}

npm i

yarn global add n
n 11.15.0
yarn install # have to install again

sudo npm i -g n
sudo n 11.15.0

> npm install --python=~/venv/bin/python

npm install gulp@^3.9.1

I have been updating all the dependencies in my js program but did not change anything with any of my components. However now when I run

npm run build

I get an error with one of my components which says:

Failed to compile.

./src/components/DonationSummaryComponent.js
  Line 14:  '_' is not defined  no-undef

Search for the keywords to learn more about each error.


npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app@0.1.0 build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:UsersItayAppDataRoamingnpm-cache_logs2018-09-17T08_25_54_825Z-debug.log

I tried

npm i lodash 

But this did not solve the problem.

Here is the component which the error is about:

import React, { Component } from 'react';
import {Alert} from 'react-bootstrap';
import {MonthlyDonations} from './MonthlyDonationsComponent.js';


export class DonationSummary extends Component {
  render() {
    var monthsComponents = [];

    var monthNames = ["January", "February", "March", "April", "May", "June",
                  "July", "August", "September", "October", "November", "December"];  

    if(this.props.yearData.length > 0){
      var monthsdata = _.groupBy(this.props.yearData, function(dataEntry) {
        return(monthNames[(new Date(dataEntry.donationDate)).getUTCMonth()]);
      });      

      for (var monthName in monthsdata) {
        if (monthsdata.hasOwnProperty(monthName)) {
          monthsComponents.push(<MonthlyDonations key={monthName+this.props.year} monthName={monthName} monthData={monthsdata[monthName]}/>);
        }
      }
    }
    else{
      monthsComponents.push(<Alert key="noDonations" bsStyle="info"> there are no donations to display </Alert> );
    }
    return(
      <div>
        {monthsComponents}
      </div>
    );
  }
}

line 14 which the error refers to is:

var monthsdata = _.groupBy(this.props.yearData, function(dataEntry) {

The error might be related to the fact that I updated react-bootstrap react to latest version (16.5.0). Both are being used in this component.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Pick a username

Email Address

Password

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

The NPM is not recognized error message is a common problem encountered by developers when using the Node Package Manager (NPM). This article will explain to you why this error occurs and what can be done to resolve it. Let’s begin!

Why Does the NPM Is Not Recognized Error Message Occurred?

The NPM is not recognized error may occured because the Node.js package manager is not properly installed on the system or if the system’s environment variables are not configured correctly. It occurs if the command is being executed in a directory that doesn’t contain a package.json file.

• Incorrect PATH variable.
• NPM is not added to the PATH.
• Conflicting installations.
• Typo in command.

– NPMIs Not Installed

When you encounter the “NPM is not recognized” error message, it could mean that NPM (Node Package Manager) is not installed on your computer. NPM is a command-line tool that is used to manage packages and dependencies for Node.js projects.

If you are trying to run an NPM command, but the system is not recognizing it, it is likely that NPM is not installed on your computer.

– Operable Program

In the context of the “NPM is not recognized” error message, the term “operable program” indicates that the system cannot find the executable batch file for the NPM package manager.

When you try to run an NPM command in the command prompt or terminal, the system first needs to locate the NPM executable file in order to execute the command. If the system cannot find the NPM executable file, it will display the error message

– Incorrect PATH Variable

The PATH environment variable is a system variable on your computer that contains a list of directories separated by semicolons (;). The PATH variable tells your operating system where to look for executable files when you run a command in the terminal or command prompt.

If the PATH variable is not set up correctly, your operating system will not be able to find the NPM executable, and you will get the “NPM is not recognized” error message.

– NPM Is Not Added to the PATH

When you install Nodejs on your computer, it also installs NPM (Node Package Manager) by default. However, if you encounter the “NPM is not recognized” error message, it could mean that NPM is not added to the PATH environment variable on your computer.

The PATH environment variable is a list of directories that your operating system uses to search for executable files when you run a command in the terminal or command prompt. If the directory containing the NPM executable is not included in the PATH variable, your operating system will not be able to find the NPM command.

– Corrupt Installation

A corrupt installation occurs when the installation of NPM (Node Package Manager) on your computer is incomplete or has become corrupted. This can lead to various errors, including the “NPM is not recognized” error message.

Here are some possible reasons why NPM installation could be corrupt:

1. Interruptions during installation: If the installation process of NPM is interrupted or stopped due to various reasons, such as network errors, power outages, or other software conflicts, it can lead to a corrupt installation.
2. File system errors: If there are errors in the file system of your computer, it can cause issues with the installation of NPM and other software.
3. Incorrect permissions: If the permissions on the directories where NPM is installed are incorrect, it can prevent the program from functioning correctly.

– Conflicting Installations

If you have multiple installations of Node.js and NPM on your computer, they may conflict with each other, leading to the “NPM is not recognized” error. You can try removing all installations of Node.js and NPM and then installing the latest version of Node.js, which includes NPM.

– Typo in Command

A typo in a command occurs when you make a mistake when typing the command in the terminal or command prompt. This can happen to anyone, regardless of their level of expertise.

If you encounter the “NPM is not recognized” error message, it is possible that you have made a typo in the NPM command that you are trying to run. For example, you might have accidentally typed “NPM” instead of “npm”, or you may have misspelled a specific NPM command.

Some error messages that can arise due to syntax or typo errors are:

• NPM’ is not recognized in VS code (visual studio).
• NPM : the term ‘npm’ is not recognized as the name of a cmdlet.
• NPM’ is not recognized as an internal or external command jenkins.
• NPM’ is not recognized as an internal or external command windows 10.
• NPM is not defined.
• NPM is not recognized laravel.

How To Resolve the Npm Is Not Recognized Error Message?

To fix the NPM is not recognized error, you have to check if NPM is properly installed and add it to your PATH environment variable. You can also try running NPM commands from the directory where it is installed, restarting your system, or running a command prompt as an administrator.

– Check if node.JS Is Installed

To use NPM, you need to have Node.js installed on your system. To check if Node.js is installed, open the command prompt or terminal and type node -v. If Node.js is installed, you will see the version number. If it is not installed, download and install Node.js from the official website.

– Check the NPM Path

If Node.js is installed, but you still get the error message, check the path where NPM is installed. By default, NPM is installed in the same directory as Node.js. You can check the path by typing where npm is in the command prompt or terminal. If the path is not correct, you can set the correct path by adding it to the system’s environment variables.

– Update the System’s Environment Variables

If the NPM path is not set correctly, you can update the system’s environment variables to include the correct path.

To do this, follow these steps:

1. Open the Control Panel and go to System and Security > System.
2. Click on “Advanced system settings”.
3. In the System Properties window, click on the “Environment Variables” button.
4. In the “User Variables” section, click on “New” and enter “Path” as the variable name and the path to the NPM installation folder as the variable value.
5. Click “OK” to save the changes.

– Restart the Command Prompt or Terminal

To apply the changes made to the environment variables, you need to restart the command prompt or terminal session. This will create a new session with the updated environment variables, allowing you to run commands and programs with the correct settings.

To restart the command prompt or terminal, close the current session and open a new one. Alternatively, you can use the command exit in the command prompt or terminal to close the current session and then open a new one. Once you have opened a new session, you can try running the NPM command again, and it should be able to recognize the command without the error message.

– Reinstall Node.js and NPM

If none of the above steps work, you can try reinstalling Node.js and NPM. Uninstall both Node.js and NPM from your system and download and install the latest version from the official website. Given below are the steps to reinstall Node.js and NPM:

1. Uninstall Node.js and NPM: To uninstall Node.js and NPM, go to the Control Panel on your Windows machine and click on “Uninstall a program”. From the list of installed programs, locate “Node.js” and click on “Uninstall”. Follow the instructions on the screen to uninstall Node.js and NPM from your system.
2. Remove any leftover files: After uninstalling Node.js and NPM, it is recommended to remove any leftover files to ensure a clean installation. You can do this by deleting the “Node.js” and “npm” folders in the following locations:

• C:Program Filesnodejs.
• C:Program Files (x86)nodejs.
• C:Users{username}AppDataRoamingnpm.
• C:Users{username}AppDataRoamingnpm-cache.

Replace {username} with your Windows username.

1. Download and install Node.js and NPM: Once you have uninstalled Node.js and NPM and removed any leftover files, download the latest version of Node.js from the official website. The installer will also install NPM.
2. Verify the installation: To verify that Node.js and NPM are installed correctly, open the command prompt or terminal and type node -v and npm -v. If you see the version numbers, it means that Node.js and NPM are installed correctly.

Conclusion

Once the article is read, you can now understand all the causes and solutions of this error easily. Below are some important points for you.

• This error is a common issue that occurs when the Node Package Manager (NPM) is not installed or properly configured on a system.
• This error can also occur when the path to the NPM executable is not set correctly or when there are conflicts with other installed software.
• To resolve the “NPM is not recognized” error, you can try reinstalling NPM, setting the path to the NPM executable, or using a different version of Node.js.
• It’s also important to ensure that any dependencies or packages required by the application or project are installed correctly.
• It’s recommended to check the documentation for the application or project, as well as online forums and support groups, for further troubleshooting steps.

Thank you for reading!