Svelte generation fails if there is an inner function

• I am interested in helping provide a fix!

Scope

• This only impacts specific generators/outputs (please list them here): Svelte

Describe the bug

Mitosis fails with an error trying to generate Svelte output for a simple component with an inner function, in this case addItem()

import { useState } from '@builder.io/mitosis';

export interface State {
  list: string[];
  newItemName: string;
}

export default function MyComponent(props: any) {
  const state = useState<State>({
    list: ['hello', 'world'],
    newItemName: 'New item',
  });

  function addItem() {
    state.list = [...state.list, state.newItemName];
  }

  return (
    <div
      css={{
        padding: '10px',
      }}
    >
      <link
        href="https://unpkg.com/tailwindcss@^2/dist/tailwind.min.css"
        rel="stylesheet"
      />

      <input
        class="shadow-md rounded w-full px-4 py-2"
        value={state.newItemName}
        onChange={(event) => (state.newItemName = event.target.value)}
      />

      <button
        class="bg-blue-500 rounded w-full text-white font-bold py-2 px-4"
        css={{
          margin: '10px 0',
        }}
        onClick={(event) => addItem()}
      >
        Add list item
      </button>

      <ul class="shadow-md rounded">
        {state.list.map((item) => (
          <li
            class="border-gray-200 border-b"
            css={{
              padding: '10px',
            }}
          >
            {item}
          </li>
        ))}
      </ul>
    </div>
  );
}
``

**To Reproduce**

Checkout current mainline.

Edit ``packages/e2e-app/mitosis.config.js` to un-comment svelte output

`yarn workspace @builder.io/e2e-app run build`

Notably, if you remove the inner addItem function, Svelte output is generated.

**Expected behavior**

Generates (valid) Svelte

Alternatively, maybe such an inner function is considered invalid Mitosis? It work OK for React, Solid, Vue (at least)

[samijaber]

I’d rather stick with creating issues until we have that system in place, to avoid the risk of forgetting what to test for. I don’t mind having tons of issues highlighting bugs 😄

[kylecordes]

I think we can close this one because the ongoing improvement of the docs to set expectations of what code works is already well-known elsewhere, right?