SSR ignores static component properties

[martinandert]

Example that does work when rendered client-side, but not on the server ("Hello, undefined!"):

<!-- App.html -->
<h1>Hello, {{name}}!</h1>
<Other />

<script>
  import Other from './Other.html';
	
  export default {
    data() {
      return {
        name: Other.NAME
      };
    },
		
    components: { Other }
  };
</script>

<!-- Other.html -->
<p>How are you today?</p>

<script>
  export default {
    setup(Component) {
      Component.NAME = 'world';
    }
  };
</script>

Perhaps there's a reason static properties are ignored for SSR, or maybe I'm just missing something obvious.

[Rich-Harris]

I think this is a bug — we should probably run setup in SSR mode. It might cause some confusion if people are using setup to e.g. wrap client-side component methods... anyone have ideas for how we could mitigate that?

[Conduitry]

Do we want it to be available somehow to the component behavior code whether it was compiled in DOM or SSR mode? Is that a terrible idea?

[Rich-Harris]

I'm going to close this as it's fixed in v3. There's no longer a setup hook — instead, a component can have named module-level exports, so it'd be done like this:

<script>
  import Other, { NAME } from './Other.html';
</script>

<!-- App.html -->
<h1>Hello, {NAME}!</h1>
<Other />

<!-- Other.html -->
<script context="module">
  export const NAME = 'world';
</script>

<p>How are you today?</p>