Malicious traffic trying to exploit path traversal in `@netlify/ipx` dependency `sharp`

[hrishikesh]

@lander

So what is the solution? I’m very confused how this can be a problem with something that’s supposed to be an SSG site.

This is a problem created by Next.js. There’s no SSG site anymore, read:

Netlify production build using SSR even when the page is specified to be built using SSG + ISR

Hello, I’ve been trying to run the production build locally to verify that my pages built using SSG + ISR works as i expect it to. I saw that running locally using “netlify dev --context production” would allow me to do this as deploying the application using “netlify dev” would deploy in development mode which defaulted page generation to SSR even if the page was specified to be built using SSG + ISR. However, using “netlify dev --context production” still results in the usage of SSR as i can…

As for:

@lander

My site is just a single page site which could be static, so I tried adding this to my next.config.js:

const nextConfig = {
  output: 'export',
};

That should produce a static site and Next Runtime correctly supports it: opennextjs-netlify/src/index.ts at main · opennextjs/opennextjs-netlify. So if you’re still seeing the Handler function, that’s unexpected.

But again, the above is only true for Runtime v5.