![]() ![]() Never use npm install on your build servers, there is a dedicated npm command for CI/CD. ![]() The first red flag was that when I looked at the CI/CD build script I saw that it was executing an npm install to install the npm packages used by the React client. ![]() Upon further inspection there was couple of issues found, that raised some red flags of some developers misunderstanding on how to build an application with npm. It was throwing errors on resolving the dependencies. The fix was purely a back-end fix behind the API, which should not have had any effect on the React client, but when the build server started building the pull request in GitHub, it was failing to build the React client. The product consisted of an API and a React client that communicated with the API. Hope this helps.An old customer reported a bug in one of the older versions of the product, and a decision was made to fix the bug and release a patch for it. I’m not sure how widespread it is, or if it’s still present in VS2017. NET 4.6 solution with a handful of projects (ASP.NET and class libraries). I’ve seen this problem frequently on Visual Studio 2015 and a. Update-Package -reinstall -Project ProjectName If you want to narrow it down to a certain project, just make sure you’ve selected the correct active project, or use this: Note: If you just run Update-Package, it will try to update all packages to the latest version, which isn’t necessarily what you want (especially if you’ve simply pulled from source control and want the project to just build with the versions of packages it has in source control). The fix for this is to open Package Manager Console and run this command: Looking in Solution Explorer, you’ll see that some packages are clearly missing (icons on the packages showing they’re not there), but no amount of telling VS to restore packages (or building, which should do the restore as well) will get them. I’ll try every way offered by Visual Studio to restore packages, but it will claim everything is up to date. Occasionally I run into an issue where I’ll open a solution in Visual Studio, build it, and the build will fail because of dependent packages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |