Elad Roz

Meanwhile, devs already have a PR ready for the next person that might stumble into it - our v5 runtime would be picked up automatically, no funny stuff needed 🙂

ah! ok... got it.
so the bottom line is we can probably improve in auto-detection or propagating the need to do anything manual. I'll pass that on!

Thanks, we'd take a look (probably not as immediately as our conversation here though...)

(and why automatic detection didn't work).
Can you send me the project name & URL in DM?

I think I know what the issue then, based on the log - it's a monorepo and the Next.js project is not at the root.

We do try automatic support these cases, but with monorepos there's like infinite ways in which folks set up their workspace. I can ask the team to advise on any manual settings

You don't need to install the plugin, it should automatically be used by builds for Next.js code.
Seems the problem is that Next.js was not detected as the framework for this site - see the line "Detected 0 framework(s)" in your log.
Did you create this project from the UI or CLI?

What's the Next.js version? how do you know you're using v4, actually?
Please take a look at the deploy log.
* In the "Initializing" stage is shows you the Node version in use.
* Then in the "Building" stage it logs what the plugin version is

I'd be glad to help figure out what the issue is, if you want.

Hey!
(I work at Netlify, including the Next.js domain)

v5 is the default for over a year for all sites with Next.js version 13.5+ (and sees a lot of usage) - unless (a) you're using an older version of Next.js, or (b) you're using Node.js < 18, or (c) you have an explicitly pinned plugin version. >

In fact, after disabling prerendering, you can try to lift the "bot embargo" in CloudFlare and see what happens - as you probably in general do want your sites indexed.

I would recommend disabling Prerendering for your site (if it's on), because it's a static site. That would mean bots which don't run JS won't load it at all (while our built-in pre-renderer would attempt load all JS and run it, because its purpose is for client-side-rendered sites). >>

Hey!
I work at Netlify.
From a quick glance at mektuplar.org, it loads a pretty hefty search index file (about 7mb). If there's a lot of bot activity (we'll release tooling for that soon), this is a likely culprit. >>

How I'm coping with the situation in Israel:
building a Lego B-2 bomber as a weekend project based on a few pictures and available parts 🤷‍♂️

Getting the canopy right (yeah, I know there is no canopy in the real thing...) took about as much time as all the rest of the superstructure.

I haven't touched React in eight years and never will again, but if you use React and especially Next.js, this is a fantastic article.

Lots of alternatives available.

That's music to
@ryansolid.bsky.social's ears! ✌️

תמצא רק חתולים

We're also good friends with the Astro team, so I'd try to get to the bottom of it when I can :-)
Also noting to @mk.gg - the CPU usage for image optimization (without the adapter) is pretty intense on my local machine, perhaps there's a way to throttle that.

Great.
I also agree that if this was automatic, it would have been great, but there are pros/cons there. Some frameworks like Next.js don't *yet* have a clear adapter interface, so we detect it automatically. Having to configure things gives you much more explicit control but is more manual.

Perhaps there were some later commits that you did there?

I've deployed a fork of the current code, and everything works very quickly (it uses the Image CDN automatically, so no time is spent in the build on optimizing images at all).
(Locally if I run a usual build, I do see it takes 2.5 minutes to optimize on an Mac M2 Pro).

I'm curious how many and how big are the images in question... is the repo public?

@astrojs/netlify Learn how to use the @astrojs/netlify SSR adapter to deploy your Astro project.

Hey, if you're using the Netlify adapter (docs.astro.build/en/guides/in...), image optimization should by default be on-the-fly rather than at build time.
(I'm from Netlify)

לחיזבאללה היה one job אבל אני רואה שהבניין הזה עדיין עומד...

אין שום בעיה בכלל.

זה הכל מקנאה, אנחנו אנשים קטנים

נקודה מעניינת אחרת בקטע היא הטענה שהמאבק בשינוי האקלים נהיה פוליטי ומפלג באשמת הסמול - ולא בגלל שיש לא מעט גורמים שיש להם אינטרס כלכלי מאוד ברור להכחיש את הבעיה, וידעו להפוך את זה לפוליטי...
מוגש בחסות "בגללכם חזרתי לתמוך בביבי"

Oh it's meant to be fed to a multi-modal LLM, of course

יותר כמו 2006 🙂