Netlify NextJS builds are broken in 3.7.0 when using multiple npm commands

[andismith]

Describe the bug
A bug has been introduced with version 3.7.0 where if the netlify.toml configuration file contains multiple npm commands such as npm run build && npm run export, the plugin fails with an internal error.

To Reproduce
Steps to reproduce the behavior:

1. Fork https://github.com/andismith/nextjs-test-blog (this is a copy of the Netlify NextJS starter blog, with an adjusted netlify.toml file).
2. Build it on Netlify
3. See error
4. Run npm install @netlify/[email protected] --save-dev
5. See it now passes

Example at: https://app.netlify.com/sites/elated-mcclintock-cdc73c/deploys

Expected behavior
The build should still work in v3.7.0

Versions

• Next.js: 11
• @netlify/plugin-nextjs: 3.7.0

If you're using file-based installation

• netlify.toml:

[build]
  publish = "dist"
  command = "npm run build && npm run export"

(this also occurs for multiple yarn commands too)

[andismith]

I think it may be a result of b1fd513

[baeteja]

3.7.0 causes issues for me as well when I use multiple npm scripts.
A temporary workaround can be to create a separate npm script where you use the other scripts.
For example: "deploy": "next build && next export"

[ascorbic]

Hi both! Thanks for the report. I've isolated the issue and opened a PR with a fix and should have that released later today.

[ascorbic]

This is now published in 3.7.1. Can you check that this fixes it for you? I've added your specific command as a test case too.

[andismith]

Thanks for attending to this so quick.

For some reason when building it in Netlify it's still picking up 3.7.0 at the latest version. I guess it takes a little while to propagate the new version. Will let you know once I can test this properly.

[ascorbic]

Yeah, we don't immediately update the auto-installed version, in case issues come up. It'll be auto-installed later today, but you can try it now by installing @netlify/plugin-nextjs@latest from npm.

[ascorbic]

If you do a build now it should use the new version of the plugin.

[andismith]

That's now working fine, thank you!