-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
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 corewaspCLI 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
npmwill solve this for us?
- Make the core functionality of Wasp CLI run correctly on Win (e.g. calling
Sub-issues
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Planned