Edge Functions not detected during deploys

[SmashManiac]

Do I have to do something more than just place a file with the JS or TS extension in /netlify/edge-functions to have it detected as an edge function during deploy? When I drag&drop my build directory in the web interface to trigger a production deploy, the log just says “No edge functions deployed” and I have no idea why could be wrong!

My site is debigare.com, for reference.

[nathanmartin]

@SmashManiac The “Drag & Drop” deploy isn’t as well supported as the other methods for deploying sites on Netlify.

It’s mentioned here that they don’t “build anything”:

[Support Guide] My drag and drop deploy is stuck in "Uploading" status

Last Reviewed by Netlify Support Staff: May 2024 Drag and drop, or "manual”, deploys are an easy way to get a simple website up and running super quick. One thing to know about manual deploys is (fun fact!) they do not generate deploy logs. This is because manual deploys don’t actually build anything, so there is nothing to log. The upside to this is that they deploy lightening fast; the downside is that, without deploy logs, we can’t tell what is happening when things go wrong or get “stuck”.…

I also know there are past threads that mention that “Drag & Drop” doesn’t support functions:

Netlify functions without connected Git repo

I don’t believe you can take advantage of functions without a git repo - to my knowledge, they don’t work with drag n drop (that’s really only for very simple, static html + css sites). You’ll need to trigger a deploy in order for your functions to get parsed, read, and become available for use, and that’s not possible without a repo. You don’t necessarily need to use continous integration - you could push manually using the CLI, for example, but you will need a deploy.

Checking the documentation I see:

https://docs.netlify.com/edge-functions/get-started/#deploy

Use continuous deployment or Netlify CLI manual deploys to deploy your edge functions.

I would avoid using “Drag & Drop” purely because it has known issues which will not be fixed and is regarded as the “least-desirable and least-capable upload method”.

See:

FIXED!: Drag & Drop Issue Status & Workaround

I managed to get a response with some transparency here: Netlify don’t believe it to be a re-occurance of the bug that prompted this thread, but simply that the “Drag & Drop” feature is inherently prone to failure. It’s dependent on things like the size of the project being uploaded, your browser memory and the stability of your network connection. The worst part of its behavior is that it doesn’t provide a timely contextual error message when it does fail, so you can end up stuck on a spinn…

[SmashManiac]

@nathanmartin

Checking the documentation I see:

Get started with Edge Functions | Netlify Docs

Use continuous deployment or Netlify CLI manual deploys to deploy your edge functions.

I read that page about 20 times and somehow missed this part. Thanks!

I’m guessing this restriction is because TypeScript edge functions require building? I wrote mine directly in JavaScript through so this restriction doesn’t seem to make much sense in that case.

Unfortunately my repo and builds have to be local, and Netlify CLI doesn’t work on my machine, so I’m kinda screwed right now.

If I knew what the Netlify CLI is supposed to do, I could potentially reproduce it locally manually as a workaround…

[nathanmartin]

@SmashManiac

I’m guessing this restriction is because TypeScript edge functions require building? I wrote mine directly in JavaScript through so this restriction doesn’t seem to make much sense in that case.

I can’t really comment on the implementation as I don’t work for Netlify.

All I know is that “Drag & Drop” deployments definitely aren’t a first-class citizen.