RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Motia] Fix pnpm version mismatch between root and motia package

There is a version mismatch for pnpm specified in the root and motia package's package.json files. This can cause issues in CI/CD pipelines and should be resolved to ensure consistency across environments.

Original Source

@@rohitg00 | 0 pts | 2/23/2026

## Bug Description The `packageManager` field specifies different pnpm versions in two `package.json` files: - **Root** `motia-js/package.json`: `"packageManager": "pnpm@10.11.0"` - **motia package** `packages/motia/package.json`: `"packageManager": "pnpm@10.19.0"` This can cause issues with: - Corepack resolving different pnpm versions depending on which directory you're in - CI/CD pipelines getting different behavior - Lockfile format differences between pnpm versions ## Expected Behavior Both files should specify the same pnpm version. Since the root manages the workspace, it should be the source of truth, and the nested package should either match or omit `packageManager` (inheriting from root). ## Environment - motia v1.0.0-rc.22 - Files: `motia-js/package.json`, `motia-js/packages/motia/package.json`

Discussion

Loading comments...