The "where do the packages even come from" section is the part I'd want more detail on. For a template pinning an exact version that's already been yanked or deprecated on the registry, does the CDN resolution just fail at that point, or do you keep some kind of version snapshot cache so old templates stay openable even after upstream changes?
Currently, CDN resolution simply fails when an exact version is gone. We do not keep snapshot backups.
Makes sense as a v1. If you ever want to harden it, caching the resolved module graph on the first successful open would keep old templates working without mirroring the whole registry, just the exact set each template pulled.
Tarun Sharma
React.js Frontend Web Developer | Next.js Specialist
The "where do the packages even come from" section is the part I'd want more detail on. For a template pinning an exact version that's already been yanked or deprecated on the registry, does the CDN resolution just fail at that point, or do you keep some kind of version snapshot cache so old templates stay openable even after upstream changes?