Update docs to show how load
differs from Next.js's getStaticProps
#813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the docs say that the
load
function is the Sveltekit equivalent to Next.js'sgetStaticProps
orgetServerSideProps
.This PR reflects the fact that Sveltekit's
load
function also runs on the client. Here's the new sentence:In Next.js,
getStaticProps
andgetServerSideProps
both only run on the server. This means it's safe to run privileged code in these functions. However, according the current Sveltekit docs,load
runs on both the client and server, meaning that you should not run privileged code in it.This PR should help prevent Sveltekit users from accidentally creating security vulnerabilities in their apps due to this difference.
Before submitting the PR, please make sure you do the following
Tests
pnpm test
and lint the project withpnpm lint
Changesets
pnpx changeset
and following the prompts