Closed SaadBazaz closed 6 months ago
Yeah I just noticed the same issue, this is related to the changes of considering Next.js as a peer dependency when building the production bundle of the library, should've created an experimental release to test this first... Anyways, this is now fixed in v5.1.1
, so upgrading to that should work.
@SaadBazaz Looks like the attempted fix in v5.1.1
did't resolve the issue, v5.1.2
is now live that contains a working fix.
@SaadBazaz Looks like the attempted fix in
v5.1.1
did't resolve the issue,v5.1.2
is now live that contains a working fix.
And due to the same recent changes there was also another issue that might cause next build
to fail depending on your environment, so upgrading to v5.1.3
addresses that as well.
/API works now!
However, some routes aren't visible at all, even though their structure is similar to the others and they're not in ignored
/API works now!
However, some routes aren't visible at all, even though their structure is similar to the others and they're not in ignored
For this issue I need more information. Generating the OpenAPI spec with the CLI, the documentation and calling the API endpoints seem to work fine in my environment with v5.1.3
. Can you describe further about your problem about your API routes not being visible and how to reproduce it.
I get a little trigger-happy when I see a new update.
Problem is, this time it broke my app and I can't understand why.
Here's the issue:
In a screenshot:
Happens whenever I access /api