Global middleware fails to call next() on a route with route-specific middleware(s) if 2nd param is a variable to an options object about hyper-express HOT 2 CLOSED

This bug has been fixed in v6.4.5. Your assumption was correct, this bug would occur because HyperExpress calculates and caches all middlewares each route has to go through into the options.middleware property internally for faster runtime performance as we only have to chain through a 1D array before calling the route handler. The problem was that the object would be directly modified, so I have now added a line to make an Object.assign copy of the provided options object and also added a test to ensure the provided options object remains immutable after route creation.

from hyper-express.

I cannot replicate this behavior on HyperExpress v6.4.2

My brain hurts, is there some evil spirit playing tricks on my codes or something
I posted this after testing like about 6 times to make sure it did indeed work on v6.4.2, but after I posted this and tried again, it decided to break, lmfao
Needless to say the stacktrace is different in v6.4.2, but yeah..

TypeError: trigger is not a function
    at Route.handle (/home/bobby/src/safe.fiery.me/node_modules/hyper-express/src/components/router/Route.js:82:28)
    at iterator (/home/bobby/src/safe.fiery.me/node_modules/hyper-express/src/components/router/Route.js:72:24)
    at /home/bobby/src/safe.fiery.me/controllers/middlewares/RateLimiter.js:47:16

And I've edited the original post with the actual cause after investigating further

from hyper-express.