fix: module exports should not be recognized as accessors

[metonym]

Fixes #56

Currently, module exports are being falsely recognized as component accessors.

<script context="module">
  /**
   * Log something (export)
   * @type {(message: string) => void}
   */
  export function log(message) {
    console.log(message);
  }
</script>

<script>
  /**
   * Log something (accessor)
   * @type {(message: string) => void}
   */
  export function log(message) {
    console.log(message);
  }
</script>

Unexpected output

/// <reference types="svelte" />
import { SvelteComponentTyped } from "svelte";

export interface InputProps {}

export default class Input extends SvelteComponentTyped<InputProps, {}, {}> {
  /**
   * Log something (export)
   */
  log: (message: string) => void;
}

Expected output

The expected behavior is that module exports should be treated as named exports.

/// <reference types="svelte" />
import { SvelteComponentTyped } from "svelte";

/**
 * Log something (export)
 */
export type log = (message: string) => void;

export interface InputProps {}

export default class Input extends SvelteComponentTyped<InputProps, {}, {}> {
  /**
   * Log something (accessor)
   */
  log: (message: string) => void;
}

The corresponding index.d.ts will also export any named exports:

export { default as Component, log } from "./Component.svelte";

Approach

• still compile Svelte source to obtain reactive_vars
• parse Svelte source to obtain instance, module, and html
• walk instance and module separately