It definitely should work. What exactly doesn't work in your case? Is the handler skipped or do you get an error?

This simplified code works as expected:

const express = require("express");

const app = express();

app.all("/api/*sth", (req, res, next) => {
        res.setHeader("my-header", "a value");
        next()
});

app.get("/*p", (req, res) => res.send("ok"));

const server = app.listen(1234, () =>
        fetch("http://localhost:1234/api/random/path").then(r => {
                console.log(r.headers);
                server.close();
        })
);

In this case it may be easier to use app.use:

app.use("/api", (req, res, next) => {
    // set headers
    next();
});

.use matches on prefix (if path is specified), so there is no need to use the * parameter.

Hi @krzysdz 👋

I think I'm also encountering a similar problem. If I have a route on /*splat it fails to match on requests to / whereas using /* would've matched on express 4.

So for example, the file

const express = require("express");

const app = express();

app.get("/*", (req, res) => res.send("ok"));

const server = app.listen(1234, () =>
	fetch("http://localhost:1234/").then(async r => {
					console.log(await r.text());
					server.close();
	})
);

Logs ok on [email protected].

After migrating to [email protected] the file looks like:

const express = require("express");

const app = express();

app.get("/*splat", (req, res) => res.send("ok"));

const server = app.listen(1234, () =>
	fetch("http://localhost:1234/").then(async r => {
					console.log(await r.text());
					server.close();
	})
);

Which logs Cannot GET / (alongside the rest of the HTML 😅).

Good catch @Tate-CC !

I did not notice it, but the path-to-regexp says

Wildcard parameters match one or more characters across multiple segments.

Looks like an optional group {} must be used - "/{*paramName}" is now (5.x) required for full compatibility with 4.x's "/*".