Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Wasp more robust (fewer wasp clean calls) #2028

Open
sodic opened this issue May 10, 2024 · 2 comments
Open

Make Wasp more robust (fewer wasp clean calls) #2028

sodic opened this issue May 10, 2024 · 2 comments
Labels
discussion hm Requires more thought shouldfix We should do/fix this at some point

Comments

@sodic
Copy link
Contributor

sodic commented May 10, 2024

This is a very, very high-level issue, but...

Most of our troubleshooting begins by telling the user: Did you run wasp clean?

This indicates low trust in wasp start and Wasp's handling of runtime changes. We should strive to reach a point where the suggestion of running wasp clean is as unreasonable as TS devs suggesting "Did you try deleting the dist folder."

This is, of course, a lot of non-obvious work, but the issue pops out all the time, and I had to document the it somewhere :)

@sodic sodic added hm Requires more thought discussion labels May 10, 2024
@Martinsos
Copy link
Member

Tangentially related to #1971 .

@Martinsos Martinsos added the shouldfix We should do/fix this at some point label May 10, 2024
@Martinsos
Copy link
Member

Here is situation in Discord where wasp clean was needed: https://discord.com/channels/686873244791210014/1239979274879111330/1239979274879111330 .
It was caused by reinstalling dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion hm Requires more thought shouldfix We should do/fix this at some point
Projects
None yet
Development

No branches or pull requests

2 participants