3 ms·
The funny thing about this is tons of developers are using Netlify for SPA's and therefore only that first request will be caught by their edge nodes, all subse
by andrewbarba 7y ago
The funny thing about this is tons of developers are using Netlify for SPA's and therefore only that first request will be caught by their edge nodes, all subsequent page views will be missed.
- timwis 7y agoWoops
- prophesi 7y agoShould be noted that Netlify provides a lot of tools for JAMstack sites, like their Netlify CMS (which you can self-host if you're determined) and Netlify Functions. If you need the SPA framework for productivity reasons, then you could use something like Gridsome to have it generate a static site.
- swyx 7y ago(i work there) lets just say this has not escaped our attention and we even discussed holding off launching until we had an easy way to log an incremental pageview from the clientside. ultimately we decided to ship first and iterate later. limiting the scope was definitely helpful running up to the launch.
- mfrye0 7y agoI was thinking the same. Realistically, I believe the only way you could do that on the client would be JS. But if they added that, it would change all their feel good marketing about no JS...