Checking a Custom Visual Into Source Control

[cboneill0099]

I have a couple custom visuals I need to check into source control.  A while back I read a blog post detailing what folders I can delete and then there is an install command to run that'll get everything I need back when I have to load the project again.  It looks like the node_modules and .tmp folders are the ones (just over 8,200 files for this particular project).

Can anyone tell me what I have to do here, or point me to where I can read up on it?

Thanks

[dm-p · Accepted solution]

Hi @cboneill0099,

If you're using Git, here's a .gitignore file you can use in your project to ensure that all temp/unnecessary files are excluded (I've had this reviewed by MS as part of certifying a visual).

As long as your package.json and package-lock.json contains all dependencies and is committed, you can rebuild your visual locally after cloning the repo by running:

npm i

...from the root folder of your project. This will scan your package*.json files and reconstruct your project's dependencies in the node_modules folder.

This should be all you need, but feel free to ask any other questions and I'll see if I can clarify for you.

Regards,

Daniel

[cboneill0099]

Thank you, appreciate the info.