Understanding function/API deployment differences

Support
1

We have a site that’s been running for the last year and the last deployment listed the functions as:

────────────────────────────────────────────────────────────────
  4. Functions bundling                                         
────────────────────────────────────────────────────────────────
​
Packaging Functions from .netlify/functions-internal directory:
 - ___netlify-handler/___netlify-handler.js
 - ___netlify-odb-handler/___netlify-odb-handler.js
 - _ipx/_ipx.js

We created a new site and deployed a separate branch but the functions listed during deployment are now:

────────────────────────────────────────────────────────────────
  4. Functions bundling                                         
────────────────────────────────────────────────────────────────
​
Packaging Functions from .netlify/functions-internal directory:
 - ___netlify-handler/___netlify-handler.js
 - ___netlify-odb-handler/___netlify-odb-handler.js
 - _api_blogs_blogType-PARAM-handler/_api_blogs_blogType-PARAM-handler.js
 - _api_catalogs-handler/_api_catalogs-handler.js
 - ...
 - _api_search_productGroup-PARAM-handler/_api_search_productGroup-PARAM-handler.js
 - _api_search_related-products-handler/_api_search_related-products-handler.js
 - _api_where-to-buy-locations-handler/_api_where-to-buy-locations-handler.js
 - _ipx/_ipx.js

The APIs listed with “PARAM” don’t work and we are trying to determine what changed. The first site shows deployment with Next.js Runtime v4.7.0 while the second/newer one shows v4.27.1. The branch of the new site works locally as well.

We also noticed in the log drains that requests to our function endpoints are listed as “(SSR)” in the original site but “(API)” in the new site. We don’t currently use a netlify.toml file.

Any pointers on where to look to understand this change would be appreciated.

3

Hey @metriedevs, it sounds like you might be running into an issue which our engineering team is already investigating. That said, I’m wondering if you can try updating the Next.js Runtime to version 4.27.2 to see if that changes the behavior? You can do this manually by adding the following in the package.json file:

"devDependencies": {
    "@netlify/plugin-nextjs": "^4.21.2"}

Let us know what you find!

5

@Amelia Thanks for the reply. I just added that dependency and confirmed that the newer version is in the build log:

9:54:18 AM: ❯ Using Next.js Runtime - v4.27.3

However, I’m still seeing the functions broken out:

9:56:44 AM: ────────────────────────────────────────────────────────────────
9:56:44 AM:   4. Functions bundling                                         
9:56:44 AM: ────────────────────────────────────────────────────────────────
9:56:44 AM: ​
9:56:44 AM: Packaging Functions from .netlify/functions-internal directory:
9:56:44 AM:  - ___netlify-handler/___netlify-handler.js
9:56:44 AM:  - ___netlify-odb-handler/___netlify-odb-handler.js
9:56:44 AM:  - _api_blogs_blogType-PARAM-handler/_api_blogs_blogType-PARAM-handler.js
9:56:44 AM:  - _api_catalogs-handler/_api_catalogs-handler.js
...
9:56:44 AM:  - _api_search_productGroup-PARAM-handler/_api_search_productGroup-PARAM-handler.js
9:56:44 AM:  - _api_search_related-products-handler/_api_search_related-products-handler.js
9:56:44 AM:  - _api_where-to-buy-locations-handler/_api_where-to-buy-locations-handler.js
9:56:44 AM:  - _ipx/_ipx.js
6

Just to clarify more on what we are seeing. We have a function in the file /pages/api/search/[productGroup].ts that we are now seeing deployed as:

_api_search_productGroup-PARAM-handler/_api_search_productGroup-PARAM-handler.js

We used to reference req.query.productGroup as the path parameter. However, we only ever get back the literal value [productGroup] in the function. As an example, the request to: /api/search/test?page=1 provides the following to NextApiRequest.query:

{ "page": "1", "productGroup": "[productGroup]" }

I’m also seeing this header in NextApiRequest.rawHeaders:

"x-matched-path" = "/api/search/[productGroup]"

We just aren’t sure what changed or what we need to do to correct this.

8

Hi, @metriedevs. I see in those logs that 4.27.3 was used. However, we were hoping to test 4.27.2.

Would you please try using this instead (so that 4.27.2 will be used)?

"devDependencies": {
    "@netlify/plugin-nextjs": "4.27.2"}

If that does not resolve this, please let us know. Also, if this doesn’t resolve this, would you please share the output of the build logs (or a link to them as our support team can see even private build logs)?

9

@Luke Thanks for the reply. My bad on the version number. I just set to 4.27.2 but am seeing the same issue. I copied over the deploy log here: Metrie-NetlifyDevBuild.20221025.log · GitHub

Please let us know if you see anything that stands out. Thanks!

10

Hey @metriedevs,

This seems to be happening with the recent change to split out API routes into their own individual functions. I can’t confirm if you’re affected by the same issue or not as I can’t any see error message inside your function logs, but to confirm (and sorry to suggest this after so much back-and-forth about versions), are you able to see this error when you downgrade to a version that didn’t use this API splitting? The last version that didn’t have this feature was v4.26.0. If by downgrading to that there are no errors, this update seems to have caused issues for you too.

12

@hrishikesh Thank you very much for replying, however, due to a deadline we ended up switching from path parameters to query string parameters. Unfortunately we don’t have the time to see this issue get resolved. Thanks again.

13

Hello @metriedevs - I can completely understand competing priorities. Thank you for your update here and if you so choose to revisit this topic at a later date, we will be here!