npm-package-arg | Parse the things that can be arguments to npm install | Runtime Evironment library

If you did using a manual installation, once you install a package using sudo, you must keep using it to install them all.

A work around to your situation may be changing your NPM's default folder

To minimize the chance of permissions errors, you can configure npm to use a different directory. In this example, you will create and use hidden directory in your home directory.

• Back up your computer
• On the command line, in your home directory, create a directory for global installations: mkdir ~/.npm-global
• Configure npm to use the new directory path: npm config set prefix '~/.npm-global'
• In your preferred text editor, open or create a ~/.profile file and add this line:export PATH=~/.npm-global/bin:$PATH
• On the command line, update your system variables: source ~/.profile
• To test your new configuration, install a package globally without using sudo: npm install -g jshint
• Instead of steps 2-4, you can use the corresponding ENV variable (e.g. if you don’t want to modify ~/.profile):NPM_CONFIG_PREFIX=~/.npm-global

Another approuch may be reinstall your NPM using a node manager package (nvm, n)

Looks to be a problem with ReactBootstrap assuming propTypes is defined in prod.

You can update your Rails babel.config.js file to ignore the babel-plugin-transform-react-remove-prop-types which is effectively what's causing the error.

You could, for example, comment the lines out, leaving a note as to why it's commented out. E.g.

There is problem with node version (12.13.1) that you are using. Uninstall NodeJs from your system and download and install NodeJS version 12.9.0 Then you wont face the issue that you have mentioned. I was having same problem as yours. but, it worked for me.

I figured it out (mostly). Due to some magic that I haven't yet sorted out, I got a reference to npm inserted into my packages.json file.

Here's what I think happened: When I ran yarn list it informed me that a newer version of yarn was available. After considerable struggling and Googling, I figured out that I could upgrade yarn and npm to the latest version via:

Clear your package-lock.json and put an empty object {}, do npm cache clean

do npm install.

that should solve the problem

I think the problem starts with node installation . Please check the node versions by using

It's caused by the CodePush task is executing the command code-push release-cordova under the default working directory $(Build.SourcesDirectory).

Since your cordova app is not in the root of the build repo, the task failed to execute code-push release-cordova command in the default working directory.

I add an issue Can not specity the directory to execute the command code-push release-cordova, you can follow up.

For Now, you can use any of below work around to build your cordova app.

CodePush task also can parse the variable Build.SourceDirectory, so you can define this variable with the value $(Build.SourcesDirectory)\path\to\cordova\app in VAriables Tab (below is an example).

When you build this task, it find the value for the variable Build.SourcesDirectory firstly (if the value is empty, then find the value in Build.SourcesDirectory).

Settings for the Command Line task as below:

Tool: cd

Arguments: path/to/your/cordova/app & code-push login & code-push release-cordova AppName OS

Below is an example settings:

Note: you should use private agent which install the code-push. If you want to use Hosted agent, you should install code-push firstly by npm install -g code-push-cli.

For TFVC repo, you should use the relative path instead of $\VisitReport_Br\Client Components\Main\Source\vr9-11.

Assume the cordova app is located in the relative path Client Components\Main\Source\vr9-11 for your TFVC repo $\VisitReport_Br as below: