Replication:

1. Creat repo using: nextjs-boilerplate (https://vercel.com/templates/next.js/nextjs-boilerplate)

Vercel

Next.js Boilerplate

Get started with Next.js and React in seconds.

3. Deploy, cloned repo, run vercel dev (had to run 'npm install next' before)
4. Create a /api folder in the root folder, added hello.ts:

1
export function GET(request: Request) {
2
  return new Response(`Hello from ${process.env.VERCEL_REGION}`);
3
}

5. Added: "type": "module" to package.json (https://vercel.com/docs/functions/functions-api-reference, following guide for 'Other frameworks' as I want my functions outside of the app folder)
6. The function works at: http://localhost:3000/api/hello
7. Added: newHello.py to /api:

1
from http.server import BaseHTTPRequestHandler
2
 
3
class handler(BaseHTTPRequestHandler):
4
 
5
    def do_GET(self):
6
        self.send_response(200)
7
        self.send_header('Content-type','text/plain')
8
        self.end_headers()
9
        self.wfile.write('Hello, world!'.encode('utf-8'))
10
        return

8. Visiting http://localhost:3000/api/newHello or http://localhost:3000/api/newHello 8.1. Or naming it to index.py and going to http://localhost:3000/api/ & http://localhost:3000/api/index & http://localhost:3000/api/index.py All return 404 errors
9. But deploying works! And the python api in the deployment works at {deployment_url}/api/newHello

So something might be messed up with my original project causing the 250MB size limit problem. But why doesn't the local api work in a brand new project, while deployed does?

Edit: Also added:

1
{
2
  "functions": {
3
    "api/newHello.py": {
4
      "runtime": "@vercel/python@4.3.1"
5
    }
6
  }
7
}

To my vercel.json, hoping it would help (normally used for Community runtimes I believe. Didn't change anything)

I moved my api file structure to the same one I created in the Replication steps with the nextjs boilerplate:

1
api/
2
   hello.ts
3
   newHello.py

I've added the following to my vercel.json:

1
{
2
  "functions": {
3
    "api/*.py": {
4
      "excludeFiles": "{.next,*.cache,node_modules,public,app,components,Docs,lib}/**,yarn.lock"
5
    }
6
  }
7
}

I've removed a test python file I had previously (testHugging.py)

Still facing the sizing issue (and local python function 404)

Copied over 100% of the files from old repo to new repo. Project now works in new repo with the python cloud function. Only difference is old repo had a parent folder, where the project lived inside a subfolder (but this was defined inside Vercel). The new repo does not have that, base folder is the project folder. Other than that 100% same files, don't know what was going wrong (had deleted .next and .vercel to see if cache problem, reinstalled node packages, etc. none of that had helped).

So only question left is, how to get it working on local

Hey, @batuhanusluel!

Great to see the progress over time.

Let us know if we can support with anything else from the Vercel side!