ignore routes for serve-static on api endpoints

I’m submitting a…

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Currently if you serveStatic alongside api routes, it would be nice if you could tell serve-static to ignore paths beginning with /api via some options. This would allow /api/not-found to return 404 from API, and not try and serve an index.html file. If there is some current way to do it, I’m also curious how I might get around this with middleware if necessary.

Expected behavior

The /api routes do not serve static on 404s.

Minimal reproduction of the problem with instructions

Run a boilerplate nestjs app with serveStatic. add app.setGlobalPrefix('api') and then try and hit /api/not-found-route-goes-here and it will serve the index.html.

What is the motivation / use case for changing the behavior?

monorepo api + webapp

Environment

Nest version: 6.12.9

 
For Tooling issues:
- Node version: v12.13.0  
- Platform: Mac  

Others:
N/A

[darrenjennings]

@kamilmysliwiec I was able to get it to work with:

exclude: ['/api/(.*)'],

I looked at the regex returned from the path-to-regexp in the isRouteExcluded util. The latest version of the library (https://forbeslindesay.github.io/express-route-tester/) returns this regexp:

// '/api*'
^\/api\/(.*)\/?(?=\/|$)

but the code in my node_modules is returning which seems to disregard that a wildcard needs to be transformed:

// '/api*'
^\/api\/\*(?:\/(?=$))?$

So it could be some dependency version resolving to an older version as it seems my lockfile has many versions of path-to-regexp. Looks my local is resolving to 0.2.5.

[kamilmysliwiec]

Follow this example https://github.com/nestjs/nest/tree/master/sample/24-serve-static (it works here)