The intent is to have .zip file with all content inside so corporate scanners could check for vulnerabilities, and after confirmation the artifact is promoted from STAGE to PROD.
NPM package format requires some dance with package.json, directory layout, etc. The final product is a hostable site by Apache/NGinx/etc, not a JS lib… At the end of bureaucracy I’ll download and unpack the ZIP (or tgz??) into a folder.
That’s why I like “raw” repository format, but storing HTML/JS among .exe/.dll files is somewhat strange…
Nexus is a corporate standard for scans & promoting to PROD, I’m trying to figure out how other teams utilize Nexus.
I’m surprised that there are no info about storing site builds as artifacts. Probably people upload builds straight to WEB server from the pipes, avoiding artifact storage as intermediary. Or stuff files into OSI container images…