Polish Wasp after the 0.12.0 release

[sodic]

Background

Release of Wasp 0.12.0 was pretty hectic and came with two major changes to the framework:

• Wasp restructuring #1688
• Injected auth models #1583

We've had to cut corners, make compromises, and leave some things unresolved. Fortunately, we've also kept the log of all the problems and potential issues we ran into (or created).

I've gone through all the notes from the different places we've used to keep track of our progress, and converted the relevant ones into GitHub issues marked with the post-0.12.0 label.

This process included notes and issues from:

• GitHub
• Notion page for Restructuring tasks
• TODOs from PR comments and unresolved PR comments
• TODOs from the code
• My local notes and todos

Issues

The issues are divided into 4 groups:

1. Regressions (affects users)
   Functionality that got worse (or even broken) with 0.12.0.
2. Fixes (affects users)
   Functionality we found out was broken while working on 0.12.0.
3. Improvements (affects users)
   Improvements to Wasp that we thought of (or created the potential for) while working on 0.12.0.
4. Cleaup (doesn't affect users)
   Internal chores and refactors for reducing the technical debt we've created while working on 0.12.0.

Groups aren't 100% clear-cut. Some issues can fit into multiple groups, but it shouldn't matter.

1. Regressions

The list includes regressions visible to our users:

• Wasp apps inside NPM projects don't work #1792
• Using AuthUI + Tailwind results in broken CSS #1764
• Explicitly type-check user code during wasp compile #1718
• Adjust the way LSP finds user's files #1717
• Improve error messages reported by the framework code #1664
• Fix Vite HMR #1829
• Prevent rollup errors from leaking to the client #1830
• Investigate and Improve Auto-imports #1839
• Can we help users distinguish their client and server JS files (and also detect wrong imports in main.wasp)? #1741
• Investigate how our file watching works #1844

2. Fixes

The list includes bugs visible to our users:

• Fix the phantom dir issue #1815
• Solve double installation issue in restructuring #1640
• Migrate examples src folder to Wasp 0.12.0  #1832
• Nodemon crashes when dependencies change #1843
• Fix Wasp directory watching #1837
• Fix dependency version checking #1859

3. Improvements

The list includes issues describing how we can improve Wasp with changes visible to our users:

• Investigate NPM workspaces and our dependency setup #1838
• Split dependencies in the new structure #1595 (comment)
• Export client config from SDK #1735
• Somehow give more context to some of the symbols exported from our SDK #1697
• Obtain user node version range from their package.json engines field #1593
• Improve how we handle user's npm deps (by aliasing wasp deps) #1644
• Design nicer imports for our SDK #1657
• Figure out Wasp's tsconfig story after Wasp 0.12.0 #1827
• Optimize SDK build step #1840
• Enforce casing conventions for all Wasp declarations #1842
• Improve how we detect whether an NPM install is necessary #1845
• Discuss DX when jumping to definitions #1847
• Auth UI and OAuth: show auth errors on screen #1817
• Change the additionalSignupFields feature to getUserFieldsFn #1608
• Enable auth validation customisation #1571
• Rethink how framework code uses user's code #1854
• Investigate whether the server can work without client file hacks #1855

4. Refactors

The list includes refactors and cleanups invisible to our users:

• Add unit tests for updates in Valid.hs #1819
• Explicitly type our public API  #1776
• Improve how we generate code (especially SDK) during wasp build #1769
• SdkGenerator/Server/EmailSenderG.hs -> genNewEmailSenderApi -> remove new from name? #1706
• Refactor our generated codebase #1841
• Small post-restructuring refactors #1846