How to set NPM_FLAGS environment variable properly?

el7cosmos · November 1, 2020, 7:55am

I set NPM_FLAGS to --only=prod --verbose from UI, but when building, i’ve got following warning:

2:48:54 PM: npm WARN invalid config only="prod --verbose" set in command line options
2:48:54 PM: npm WARN invalid config Must be one of: null, dev, development, prod, production

How to set NPM_FLAGS properly?

fool · November 6, 2020, 12:02am

hi there @el7cosmos and welcome to our community!

This is the line in our build scripts when we use them:

github.com

netlify/build-image/blob/xenial/run-build-functions.sh#L149


      
          restore_home_cache ".yarn_cache" "yarn cache"
          
          
if [ $(which yarn) ] && [ "$(yarn --version)" != "$yarn_version" ]
          then
            echo "Found yarn version ($(yarn --version)) that doesn't match expected ($yarn_version)"
            rm -rf $NETLIFY_CACHE_DIR/yarn $HOME/.yarn
            npm uninstall yarn -g
          fi
          
          
if ! [ $(which yarn) ]
          then
            echo "Installing yarn at version $yarn_version"
            rm -rf $HOME/.yarn
            bash /usr/local/bin/yarn-installer.sh --version $yarn_version
            mv $HOME/.yarn $NETLIFY_CACHE_DIR/yarn
            export PATH=$NETLIFY_CACHE_DIR/yarn/bin:$PATH
          fi
          
          
restore_node_modules "yarn"
          
          
echo "Installing NPM modules using Yarn version $(yarn --version)"

I didn’t go to deep into why that is happening since I discovered that --verbose --only=prod (no explicit quotes in my settings, just for clarity here!) seemed to work better for me - could you let me know if that works better for you too?

el7cosmos · November 6, 2020, 5:42pm

It didn’t throw a warning, but no verbose output.

I try in my local following command:

npm install "--only=prod --verbose"

throws same warning, and

npm install "--verbose --only=prod"

didn’t have verbose information.

I think thats because either shell or npm treat those as 1 argument instead of 2 or multiple

jen · November 13, 2020, 7:43pm

Hey @el7cosmos, this seems like a bug to me. When I set NPM_FLAGS to either --verbose or --only=prod seems to work, but setting the variable to both doesn’t seem to work. I’ve opened an issue here (NPM_FLAGS doesn't handle more than one flag · Issue #496 · netlify/build-image · GitHub) and we can let you know if/when there’s movement on it. Or if this is urgent for you, I’m sure the build team would love a PR!

jgantunes · July 16, 2021, 2:45pm

Hey folks

For anyone following this post, just wanted to let you know that thanks to an awesome contribution to our OSS build-image repo, this issue has been fixed and rolled out to our xenial and focal releases.

Thank you all!

Topic		Replies	Views
YARN_FLAGS env variable being ignored Support building , environment-vars	23	2088	December 2, 2021
Don't reflect environment variable for npm Support deployment	1	639	January 21, 2020
Node v16.15.1 (npm v8.11.0) breaks some builds Support building , deployment	20	13848	October 8, 2022
NETLIFY_USE_YARN in config.toml not working Support environment-vars	4	1198	June 29, 2021
NETLIFY_USE_YARN environment variable ignored Support deployment , monorepo	1	761	May 31, 2021

How to set NPM_FLAGS environment variable properly?

Related topics