10.0.8 breaks plugin (can't read config target)

[laugharn]

Describe the bug
We are experimenting with using netlify-plugin-nextjs instead of next-on-netlify in a yarn monorepo. Unfortunately, when we attempt to deploy with the plugin, we get a Your next.config.js must set the "target" property to one of: serverless, experimental-serverless-trace. Update the target property to allow this plugin to run. message. Attached are two screen shots, one of the next.config.js in question, and the second of the message:

As you can see from the message screenshot, it is console logging This file is detected based on the next.config.js console.log statement, so it sees the correct file. I can also confirm that this is working if we use next-on-netlify directly.

Expected behavior
Successful deployment

Versions

• Next.js: 10.0.8-canary.10
• plugin (if installed at fixed version): @netlify/plugin-nextjs@2.0.1 via UI install

[lindsaylevine]

@laugharn hey dan! this seems like possibly a monorepo-specific problem? unfortunately i'm not able to repro off this info alone :(. are you able to open a simple [mono]repo that imitates your general setup/dir structure and repros this error? 🙏

[laugharn]

Hi @lindsaylevine, I've done a little bit more work and this appears to be a 10.0.8-canary issue, it builds correctly with 10.0.7

I'm doing the exploration at https://github.com/bungalohomes/exp building the main directory. I'm not sure how much access you have at Netlify but I can point you to some of our deployments/logs.

[lindsaylevine]

@laugharn

1. ok good to know @ 10.0.8-canary
2. i can see whatever you link me so send it over! :)

[lindsaylevine]

just checked, this is an issue for more than just monorepos. digging in now.

[segheysens]

Similar, I had to upgrade to Next 10.0.8-canary because of challenges with the sharp package on an M1 Macbook. Confirming that I'm seeing this error as well. Thanks for the quick work on that PR @lindsaylevine, lmk if there's any extra context I could share to help close this one out!

[lindsaylevine]

@segheysens thanks stephen!! working on it!! requires a big refactor 😅

[brenelz]

I think I ran into a similar problem today with deploying next js 10.0.8. Nice work jumping on it so quickly!

[lindsaylevine]

fixed and released in v3.0.0!

[brenelz]

yay thats awesome I just tried it and it worked! I uninstalled and reinstalled the plugin to get the latest version not sure if required or not.

[lindsaylevine]

@brenelz if you had the plugin installed at a fixed version before, then you'd need to reinstall :) otherwise it should run on the latest!