You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case is that the data my landing page is loaded with from getStaticProps is exactly what i'd like exposed via api for integration partners.
I see that when I load the page, next hits an endpoint like _next/data/0R0O1Fr.../index.json for the page props JSON, but I doubt that link is meant to be shared or used externally, so I'm wondering if there's a way to create a more permanent public URL with the same result?
The other option I saw was to just move what's in getStaticProps to a lambda, but my understanding was that refactoring the landing page to fetch from a lambda be strictly slower than using static props.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My use case is that the data my landing page is loaded with from
getStaticProps
is exactly what i'd like exposed via api for integration partners.I see that when I load the page, next hits an endpoint like
_next/data/0R0O1Fr.../index.json
for the page props JSON, but I doubt that link is meant to be shared or used externally, so I'm wondering if there's a way to create a more permanent public URL with the same result?The other option I saw was to just move what's in
getStaticProps
to a lambda, but my understanding was that refactoring the landing page to fetch from a lambda be strictly slower than using static props.Beta Was this translation helpful? Give feedback.
All reactions