[Bug?]: createHandler context only called once, renders nonce useless

[paularmstrong]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

Related to #1440

In production mode, the options object passed to createHandler is only ever evaluated once on startup (or maybe first request?). This renders setting a nonce in the context useless, because it will always be the same value.

Expected behavior 🤔

If the HandlerOptions is a function, it should be executed for every page event/request and not done on initial startup.

Steps to reproduce 🕹

Steps:

Create the entry-server with an function (async or not) that gets and returns a unique nonce value:

export default createHandler(
  (context) => {
    return <StartServer>{/* ... */}</StartServer>;
  },
  async (event: PageEvent) => {
    await getNonce(context);
    return { nonce };
  }
);

View page output and notice that the nonce never changes.

Important

This is only reproducible when the server is built and run – it does NOT reproduce in dev mode.

Context 🔦

https://content-security-policy.com/nonce/

Your environment 🌎

n/a

[paularmstrong]

Thank you @ryansolid ! I was having a tough time tracking this down today