Updated NPM dependencies don't install

I'm using TeamCity to install npm dependencies as part of the build process, there is one dependency that is installed from our local npm registry so it looks like this. 

// .npmrc

@customscope:registry=http://proget.customscope.com:8624/npm/Frontend/

then in my package.json

"@customscope/components": "~0.0.1"

This is working, npm install on the TeamCity server respects the .npmrc file and looks to the proget.customscope.com server

The problem is TeamCity does not get the latest version

So when @customscope/components version is bumped to 0.0.2, the npm command in TeamCity still installs 0.0.1

In the VCS settings I've put a check in "Delete all files in the checkout directory before the build"

Is there something in NPM that I need to do to ensure it always gets the latest version?

This issue is not happening outside  the TeamCity environment

 

0
1 comment

Hi Shane,

 

if the issue doesn't happen in your environment, please follow the steps here for troubleshooting: https://confluence.jetbrains.com/display/TCD18/Common+Problems#CommonProblems-BuildworkslocallybutfailsormisbehavesinTeamCity

 

 

0

Please sign in to leave a comment.