Next Build Registry.json

[mreed101]

Description

Vets-website applications are currently injected into content-build via a registry.json file that lives inside of the content-build repository. We need to mimic this functionality for next-build. This ticket is to determine the best place for that registry.json file to live and create it.

Supporting Detail

Inside of vets-website there is an app-manifest that is generated for all of the applications in that repository. It would be worth determining if we could have that file generate a registry.json file that could then be grabbed by next-build. This would prevent developers from needing to make updates in 2 separate repositories. We already grab multiple items from vets-website that are stored in the next-build > public > generated folder and this could be a suitable location.

Screenshot

N/A

Task

• Registry file recreated
• Process documented inside of ReadMe