In a solution setup with a RCL with
# package-development
k
In a solution setup with a RCL with wwwroot as output dir and an Umbraco project that reference this library for assets to be served from compilation. What's best practice to avoid repo from being "polluted" with constant new filenames of the frontend output in the RCL wwwroot directory? I guess those files needs to be in repo? or?
s
I don't understand what files your seeing pop up where?
Afaik this is a fairly typical setup. Just annoying with the noise in a commit the files (with cache busting filenames) introduces.
s
Ah I see! You can gitignore those, they will be generated when you
npm build
.
k
yeah and do the build in the ci/cd pipeline
ok, that worked - but I had to delete cached images and files in the browser for it to get the latest version og the vite build.
s
yeah need to clean it up once an dthen it should "just" work for consecutive builds! 👍
k
ok, tnx!