Original Summary

I built hidane because the Firestore emulator had become the slowest, heaviest part of my test runs, and firebase-tools 15 made Java 21 a requirement for it. hidane is a reimplementation of the emulator as one Rust binary: it starts in about 5.5 ms and idles at 7.4 MiB (the official one: 0.74 s and 95 MiB, measured on different machines; a same-machine run is planned). The part I care most about is the rule I set myself: no claim of compatibility without a test behind it. Scripts send the official emulator thousands of requests, edge cases included, and record its answers; hidane's test suite replays all 20,224 of them. Where the official emulator has a bug, hidane doesn't copy it, and every difference is written down. Where it is now (0.4.0, released today): gRPC, REST and WebChannel on one port, so the Admin SDK, the web SDK and Flutter Web connect unchanged Security Rules, with the official denial messages runs under firebase-tools: hidane exec -- firebase emulators:start new in 0.4: Firestore-triggered Cloud Functions fire with the same data as with the official emulator It's free and open source (MIT OR Apache-2.0), a side project by one person. What I'd like feedback on: if you run Firestore tests locally or in CI, what would stop you from swapping the emulator? And if anything gives you a different answer than the official emulator, that's a bug I want to hear about. https://github.com/hidane-dev/hidane   submitted by   /u/nomunomu0504 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/13 09:25:16