TypeError: (0 , import_react.cache) is not a function

[markedwards]

Getting this error on a bunch of paths, all of which are outside of my allowedPaths config. This started happening with 6.0.3.

Error while importing /api/marketer/conversations/{conversationId}/response, skipping path...
TypeError: (0 , import_react.cache) is not a function
If you don't want this path to be part of your generated OpenAPI spec and want to prevent seeing this error in the future, please add /api/marketer/conversations/{conversationId}/response to 'deniedPaths'.

Not sure what the error is, but also not sure why these paths are being considered since they are not in allowedPaths.

[markedwards]

Seems to be mitigated by using --configPath. However, I still end up with a long list of "ignored" paths, which are not in the allowedPaths.

[blomqma]

Seems to be mitigated by using --configPath. However, I still end up with a long list of "ignored" paths, which are not in the allowedPaths.

Thanks. The error you're seeing is coming from the process of finding the correct docs route containing the config to use for building the OpenAPI spec, for which we can silence errors like this, I'll get it fixed 👍🏻

[blomqma]

This should be fixed in v6.0.5.

[markedwards]

Thanks for the quick fix.

Does it make sense to only examine directories that match the allowedPaths? It seems wasteful to look in other places. Or maybe I misunderstand that feature.

[blomqma]

Thanks for the quick fix.

Does it make sense to only examine directories that match the allowedPaths? It seems wasteful to look in other places. Or maybe I misunderstand that feature.

File paths that are not included in allowedPaths are not parsed for generating the OpenAPI paths: https://github.com/blomqma/next-rest-framework/blob/main/packages/next-rest-framework/src/cli/utils.ts#L210

For finding the config from the docs route(s), we don't know the value of allowedPaths before we find the config to use, neither is it useful since the docs routes are not supposed to be included in allowedPaths.

[markedwards]

Of course, I'm being stupid.

Thanks.

[markedwards]

Running into this again, this time from an import in an API path. It's happening when some code imports cache from react.

Is this expected? Why does this fail? I guess its necessary to be inside a react rendering context for cache to be available?

[markedwards]

Using cache() in a route handler does work fine, so I think this is just an issue when next-rest-framework explores for routes.

Can this be fixed? Should I open a separate issue for it?