Skip to content

Windows (WSL, native) support #2890

@Martinsos

Description

@Martinsos

Must

  • Ensure Wasp works well in WSL and experience is good. Test the happy path. Allegedly there are performance issues that are easy to hit, and there are other stumbling blocks for people. We should identify those and address them the best we can (via code, via docs, …). Make using Wasp in WSL a good, predictable experience.
    This might be covered by “happy path” epic already.

Should

  • Make Wasp run natively on Windows. Comes down to two main things:
    • Make the core functionality of Wasp CLI run correctly on Win (e.g. calling npm, encodings, have that being run and tested in CI, ...): Get core wasp CLI functionality working on Windows #3148
    • Hunting down non-core POSIX-specific logic and adding alternative Win-logic or disabling the feature on Win. e.g. wasp start db.
    • Packaging Wasp so it can be easily installed on Windows. Maybe installation via npm will solve this for us?

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Status

    Planned

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions