Rename `context` to `stuff`

There are a couple different places we use the word context

• load has a context parameter
• getContext sets request.context

Adding this here to track and have a discussion at some point since a couple maintainers have mentioned this as being something we might want to considers

Also, it looks like perhaps we should fix this TODO in the process: https://github.com/sveltejs/kit/blob/08ebcb518c71cd58f4717784a5144cb195b49a68/packages/kit/src/runtime/server/page/respond.js#L178

[dummdidumm]

Since context just fits best if it wasn’t taken already, I propose layoutContext or loadContext to show a) the semantic similarity to contexts but b) make it visible that this is different and belongs to a specific part. The drawback of a few more keystrokes is a hit I’ll gladly take.

[Rich-Harris]

The core team just had a long conversation about this and we like request.locals instead of request.context. Rather than having a getLocals(request) function we can do request.locals = {} before we pass it into handle:

function handle({ request, render }) {
  request.locals.user = get_user(request);
  return render(request);
}

function getSession(request) {
  return {
    user: sanitize_user(request.locals.user)
  };
}

We also spent entirely too long trying to come up with an alternative to layout context, but couldn’t come to agreement. Some ideas that were floated, in no particular order of terribleness:

• inherit
• inherits
• inherited
• pipe
• chain
• context (keep as is)
• locals (again)
• tunnel
• metadata
• env
• scene
• domain
• foo
• $layout