Wasp

Public discussion around Wasp over the past four weeks was dominated by frustration with bugs and reliability concerns, with complaint-side themes outpacing praise by a wide margin across the 18 mentions captured in the window. Bug reports accounted for the single largest cluster of discussion, and reliability concerns were close behind, suggesting that a meaningful share of commenters were encountering issues serious enough to surface publicly. Several mentions pointed specifically to problems with file extension handling in generated TypeScript output, with discussion suggesting that extensionless import expectations were clashing with how the tool was emitting paths, causing build failures for some users.

The score trajectory tells a clear story of gradual erosion followed by a sharper drop. Sentiment opened the window in a noticeably more positive position in late March, then drifted downward through April and into May before a brief and modest recovery around early June. That recovery did not hold: the week of June 8th saw the lowest point in the tracked window, coinciding with the largest single-week burst of mentions, and the final week showed only a partial rebound. The pattern suggests that higher engagement was associated with more negative sentiment rather than renewed enthusiasm.

On the praise side, discussion was thin and scattered across ease of use, a new feature release, and integration positives, but none of these themes generated the kind of volume or energy to meaningfully offset the complaints. Feature gaps and integration shortcomings added further weight to the negative side.

Opinion appeared divided primarily around the development tooling and ecosystem direction. Several mentions reflected active internal or community-level debate about environment requirements, dependency management practices, and how the spec packaging model should work, with some commenters framing these as forward-looking infrastructure questions and others treating them as current friction points.