[Bug]: NETLIFY_NEXT_PLUGIN_SKIP no longer works in v5 about next-runtime HOT 7 CLOSED

Hi. Thanks for the report. It loioks like this is a bug related to the way we now handle export. In the new runtime we do handle sites that use output: "export", so it doesn't need to be disabled. However it does need the publish dir to be set to .next. We should be handling this gracefully though, so this will be fixed. In the meantime, manually setting it back to .next will mean it works again, and you will get the benefit of things like caching from the runtime.

from next-runtime.

No worries, I've reverted back to V4 runtime for the time being.

For anybody seeing this, this how to do that:

1. Create a netlify.toml file (if you havent already got one)
2. Paste the following into this file:

  [[plugins]]
  package = "@netlify/plugin-nextjs"

3. Install the dependancy @netlify/plugin-nextjs@4

from next-runtime.

The publish dir of .next is not an optimised build in comparison to the out folder. This needs to be out.

Hi. Thanks for the report. It loioks like this is a bug related to the way we now handle export. In the new runtime we do handle sites that use output: "export", so it doesn't need to be disabled. However it does need the publish dir to be set to .next. We should be handling this gracefully though, so this will be fixed. In the meantime, manually setting it back to .next will mean it works again, and you will get the benefit of things like caching from the runtime.

from next-runtime.

All my sites are currently broken due to this, is there no way to force netlify to use version 4 of runtime whilst this is fixed? @ascorbic

from next-runtime.

The runtime handles it - it doesn't publish the actual .next files, but it expects that to be the publish dir so that it can find the generated config. We should be handling it gracefully though, so this is just a workaround.

from next-runtime.

Hi. Thanks for the report. It loioks like this is a bug related to the way we now handle export. In the new runtime we do handle sites that use output: "export", so it doesn't need to be disabled. However it does need the publish dir to be set to .next. We should be handling this gracefully though, so this will be fixed. In the meantime, manually setting it back to .next will mean it works again, and you will get the benefit of things like caching from the runtime.

This worked for me. Thanks!

from next-runtime.

The fix for this is in version 5.1.2 of the runtime, which will roll out to users over the next day or can be installed manually if you want it now. With that you don't need to do anything with the publish dir, as we'll detect the correct location for where it is being built.

from next-runtime.