Kartik
Kartik
I see, I will look into integrating this using native RegExp If possible for the best performance.
> Sounds like a bad idea Overall, I would agree with this sentiment for the time being. I think RegExp based routes open up possibilities for unexpected behavior as the...
Hello, as you may have read from previous issues and documentation, the `hyper-express` middleware system at the moment is very different from Express.js in both its operation and internal logic....
Hey, good catch! Do you want to make a PR to fix this typo?
Could you provide a reproducible example? I believe the example snippets already have tests for them which would fail If they were not behaving properly?
This seems to occur because the id is incrementally generated at runtime to maintain the assignment order. The problem is that making any changes to this behavior might be a...
This bug has been solved in the recent `v6.17.2` version of `hyper-express`. @RohinBhargava Your solution worked perfectly. Feel free to make a PR in the future. Apologize for the long...
Hello, yes with localhost it is possible to strain the Node to C++ overhead due to the fast volume and little queueing or delay in the localhost communication. The best...
> It's not about extracting the token. It's about throwing an Error instead of using `next(Error)`. It's seems throwing causes the app to crash whereas using `next(Error)` doesn't. But both...
Hey, I am looking into this now. It seems that the error may be escaping the global handler when not explicitly passed to `Next` while this should not be the...