Forum Discussion
Warnings when doing gulp bundle
Hi Christian,
Is this a solution that you're opening from source control, or something you've completely written in your environment?
The first thing I'd do is delete and rebuilt the entire node_modules folder
rm rf node_modules npm iIf you're not working on this together with a group of people who all need to be on the same exact version of the project (for example if you are working alone in your environment, but you cloned the project from github) I'd delete the package-lock.json file as well before npm i
Hi Christian,
Is this a solution that you're opening from source control, or something you've completely written in your environment?
The first thing I'd do is delete and rebuilt the entire node_modules folder
rm rf node_modules
npm i
If you're not working on this together with a group of people who all need to be on the same exact version of the project (for example if you are working alone in your environment, but you cloned the project from github) I'd delete the package-lock.json file as well before npm i
thanks for your tips. Initially it didn't work but there were two library components which we developed linked to the solution. So I repeated the same steps for both libraries and after that the warnings disappeared.
I also deleted the package-lock.json in the main solution and the libraries. Why do you think that could be a problem for colleagues working together with me? I looked in our source control system and saw that neither the node_modules nor the package-lock.json are checked in there. So everyone has it's own version of that anyway and the others had no warnings when doing gulp serve on solutions using the library components.
