Invalid Hook call in dynamic routes

[kush-daga]

Describe the bug
In my next.js website, the dynamic routes, are throwing an error.

These work fine locally, and give no errors.
This can be related to using of esbuild as node_bundler.

Expected behavior
The dynamic routes should work, as they do locally.

Versions

• Next.js: ^10.2.0
• plugin (if installed at fixed version):

If you're using the CLI to build

• OS: [e.g. macOS, Windows]
• netlify/cli version:

If you're using file-based installation

• netlify.toml:
  

[kush-daga]

Definitely seems like a netlify plugin issue, as tested the same by deploying on vercel, and it works as expected

[lindsaylevine]

@kush-daga hey! thanks for reporting this to us! can you please provide a simple and deployable repo that reproduces your issue? it can have just a single failing dynamic page. thank you!

[kush-daga]

@kush-daga hey! thanks for reporting this to us! can you please provide a simple and deployable repo that reproduces your issue? it can have just a single failing dynamic page. thank you!

Heyy! Thanks for your reply, I did recreate this issue,

This is the url -> https://romantic-gates-22561a.netlify.app/dynamic/1
GitHub Repo -> https://github.com/kush-daga/next-netlify-bug

Works perfectly on local

[kush-daga]

Also I have the NETLIFY_EXPERIMENTAL_PROCESS_DYNAMIC_IMPORTS set totrue in my netlify env variables

[lindsaylevine]

hey @kush-daga! switching to target: serverless from target: experimental-serverless-trace should fix your issue. let me know and we can close :)!

[lindsaylevine]

and ftr, the NETLIFY_EXPERIMENTAL_PROCESS_DYNAMIC_IMPORTS flag is no longer needed for esbuild to work with dynamic imports!

[kush-daga]

hey @kush-daga! switching to target: serverless from target: experimental-serverless-trace should fix your issue. let me know and we can close :)!

Hey, umm I wanted to do this, however I am using sentry in my app, which requires this mode of target, as per this comment getsentry/sentry-javascript#3621 (comment)

[lindsaylevine]

hmm. i pinged our esbuild expert internally to see what might be up. in the meantime, is it possible to omit one of the three offending features? (aka e-s-t, esbuild, or sentry?) or are all three required for your use case?

note that we will "soon" be moving off of target: serverless to target: server. not in the very near future, but eventually.

[kush-daga]

hmm. i pinged our esbuild expert internally to see what might be up. in the meantime, is it possible to omit one of the three offending features? (aka e-s-t, esbuild, or sentry?) or are all three required for your use case?

note that we will "soon" be moving off of target: serverless to target: server. not in the very near future, but eventually.

Hmmm, I wish i could omit one, but seems like all three are required for now, thanks for the reply though, will be waiting on an update :)

[ascorbic]

Hi @kush-daga
I managed to reproduce this issue. Removing next from external node modules fixes it for me. Was there a reason you needed to add it? Let me know if it works for you.

[ascorbic]

Ah, I realise the error message was suggesting it. We will fix that. To be clear: you shouldn't add next to external node modules, whatever the message says.

[sidwebworks]

any update on this? I am struggling to deploy this on netlify, it works fine on vercel but my entire stack is on netlify so I wanna build there

[lindsaylevine]

@SidRathi47 my teammate matt provided updates earlier in the day. also, there are two solutions listed in the comments so far:

1. remove next from external_node_modules if you have it in your netlify.toml (like kush-daga)
2. change to target: serverless

we know nothing about your specific use case as you've only just commented. do those updates and solutions not suffice for you? what further update are you looking for?

[kush-daga]

Hi @kush-daga
I managed to reproduce this issue. Removing next from external node modules fixes it for me. Was there a reason you needed to add it? Let me know if it works for you.

Hey, sorry was a bit busy, will check and get back on this asap.

[kush-daga]

Hey! just checked, removing next from external node modules fixed it. Thank you so much @ascorbic, @lindsaylevine

[lindsaylevine]

yay, thanks for letting us know!!