Skip to content

[TS] Ensure WASM Build Works In Both Browser And Node (etc) #56

@jbolda

Description

@jbolda

Motivation

With the implementation of WASM, it isn't always incredibly easy to ensure that file is included in a library and appropriately loaded downstream.

  • ensure that it runs in Node (Deno would also be nice)
  • ensure it runs in the browser (effectively complete by integrating with the playground)
  • ensure it works in downstream plugins
    • VSCode extension
    • Astro integration (technically browser, but seems to require a loader due to Vite handling, documentation required)
    • Obsidian integration

If any of these situations requires special handling, we also need to specifically document these situations. It isn't required to document for each specific plugin, but the general documentation should represent and include information that would be relevant to implementers of those plugins.

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions