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.

[PostHog] Support source map resolution for WASM errors

PostHog's current source map resolution mechanism, which relies on chunk IDs in JavaScript files, is incompatible with WebAssembly (WASM) binaries. This prevents proper error tracking and debugging for WASM applications.

Original Source

@@yawn | 0 pts | 2d ago

### Feature request ## Is your feature request related to a problem? PostHog's source map resolution requires chunk IDs injected into served JavaScript files (//# chunkId=...). The JS SDK reads these comments at error time to match frames to uploaded source maps. This doesn't work for WebAssembly. WASM binaries are not text files — there's nowhere to inject a chunk ID comment, and the SDK can't read one from a .wasm file. As a result, WASM source maps cannot be resolved even when correctly generated and uploaded. ## Describe the solution you'd like Native support for WASM sourcemaps (similar to dsym, hermes, proguard support). ## Describe alternatives you've considered - Allow passing a chunk id when reporting errors to PostHog - this way we could upload WASM sourcemaps in the v3 sourcemap format and explicitly send the chunk id required for you to do the matching (e.g. hash of the wasm file) - Enable matching on filenames only - this would require release-specific asset names (

Discussion

Loading comments...