-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
TODO
- Refine this more, these are now just some issues we thought of first. Look at issues marked with
dxlabel. - We need to do a bit of a research here: look at open issues, do some happy path testing ourselves, observe some users try to use Wasp for the first time, and also ask in Discord. Then we can paint a full picture of all the points where people fail / get stuck.
- If this turns out to be too big of an epic, consider splitting it into mutliple (sub)epics.
Must
- Better CLI experience
- nicer (e.g. less noisy) output → look at others
- [Carlos] Smarter CLI (e.g.
wasp startdoesn't crap out if you don't have a DB, it asks if you want it to spin it for you)
- Better documentation
- better sidebar organization in the docs?
- nicer looking tutorial app
- [Filip] Properly documenting our public API (issue).
- reference of API in the docs that is auto-generated
- [Filip] Make our docs feature complete (e.g., stuff like this)
- Learning materials → make them proper guides/recipes/cookbooks in the docs (issue)
- Make sure users can easily discover richer documentation for features in tutorial #2079
- We are missing docs on Page and Route #2072
- Reorganize docs sidebar #2071
- Fix code blocks color in dark theme #1983
- Fix incorrect extensions for ext import in our docs #2385
- fix our file watching (nodemon, deps)
- fix flaky
wasp start- related: 1843.
- improve slow npm install
- npm workspaces should also help (no duplication)
- Check if we can skip it sometimes
- pnpm
- Check what is happening on WSL for some users
- [Filip] Support changing ports in Wasp apps (issue)
Some possibly related issues
- Improve how Wasp handles and reports unavailable ports #2427
- Building SDK step doesn't mark error output as coming from stderr, with ! in [ Wasp ] #2328
- Database setup step in
wasp startreports success even when it fails #2327 - Improve visibility of wasp errors and warnings during wasp start (especialy prisma migrate) #2326
- Make Ext import extensions consitent #2222
- Wasp doesn't correctly detect failed npm install and continues instead of stopping #2196
- Improve error message when correct version of
npmisn't inPATH#2113 - Can we have better error messages for TS5097: non '.ts' extension used in a query or operation ext import #2087
- Make Wasp more robust (fewer
wasp cleancalls) #2028 - Optimize SDK build step #1840
- Fix Wasp directory watching #1837
- Replace the
pngWasp logo with ansvgin default template #1534
Sub-issues
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Planned