# Streaming regexp support **URL:** \ **Category:** 💡 Ideas\ **Created:** [January 24, 2020, 7:42am UTC](https://es.discourse.group/t/streaming-regexp-support/205 "2020-01-24T07:42:56Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![claudiameadows](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/claudiameadows/32/126_2.png) [@claudiameadows](https://es.discourse.group/u/claudiameadows)\ **Post date:** [January 24, 2020, 7:42am UTC](https://es.discourse.group/t/streaming-regexp-support/205/1 "2020-01-24T07:42:56Z")
[Link to repo](https://github.com/isiahmeadows/streaming-regexp-proposal/) Back in 2018 I created that repo with a strawperson, and I feel that it's very necessary for streaming APIs where matches may occur across chunk boundaries and for as-you-type validation where you might want to notify the user when they type an invalid character but not if they're still typing out a potentially valid sequence. The repo itself documents much of the rationale, but the state of the JS world in that area hasn't hardly changed at all. Thoughts? * * * I do want to note I'm by no means married to the names or the particular API, and am open to suggestions in that front. (Integration with iterables of UTF-8 and/or UCS-2 sequences is a must, though, as well as the ability to read strings.) ---
**Author:** ![conartist6](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/conartist6/32/515_2.png) [@conartist6](https://es.discourse.group/u/conartist6)\ **Post date:** [November 22, 2020, 3:51pm UTC](https://es.discourse.group/t/streaming-regexp-support/205/2 "2020-11-22T15:51:12Z")
Oh hey, I am working this right now in fact. It will be a package called `@iter-tools/regex`. I haven't published the package (or even uploaded my repo) yet though. I decided to build it because like you I could find any implementation that didn't have problems with chunk boundaries. My code was mostly working, I just had to take a step backwards to implement zero-width matches.