UNLESS method does not work with restify v11

[renatomotorline]

Describe the bug
Hi, I'm trying update to restify 11.0.0. But when I put the restify-jwt-community middleware I start to get on all request this error:
Error [ERR_HTTP_HEADERS_SENT]: Cannot render headers after they are sent to the client
Even if the request is on the unless path.
If I comment server.use(rjwt({ secret: config.JWT_SECRET }).unless({path: ['/auth/token']})); the requests that don't use jwt token start to work fine.

UPDATE NOTE:
If remove the unless works fine.
As alternative to unless I did this:

server.use(rjwt({ secret: config.JWT_SECRET }), function (err, req, res, next) {
    if (err) {
        var path = [
            '/path1',
            '/path2',
        ];
        var matches = path.filter(function (pattern) {
            return new RegExp(pattern).test(req.url);
        });
        // If url match some path
        if (matches.length > 0) {
            return next();
        }
        return next(err);
    }
    
    return next();
});

To Reproduce

const rjwt = require('restify-jwt-community');
server.use(rjwt({ secret: config.JWT_SECRET }).unless({path: ['/auth/token']}));

Expected behavior
This code on restify 8.5.1 works fine.

System:

• OS: Docker node:16-alpine
• Restify JWT Community version 1.1.29

[frbuceta]

Can you test if it works with version 2.0.0.0 of the package?

[mohammad-mahmoodi]

No, it does not work in version 2.0.0 either.

[Joeao]

Experiencing this with 2.0.0, using restify 11.1.0.

The reason for Error [ERR_HTTP_HEADERS_SENT]: Cannot render headers after they are sent to the client being seen is that each following request is being triggered twice.

I've implemented the workaround provided in the original comment, which works just fine.

[MaikelFC]

Also encountered this problem using 2.0.0 and restifiy 11.1.0,
The work around in the original comment worked for me.

Took forever to find out what was causing the request to process twice.