My question is : If --ignore-engines "fixes" the problem (i.e. it ignores the warning), why not pushing a new version of this module with adding Node 18 to the engine requirements? Is there _really_ an incompatibility, or is this message simply because v18 is missing from the engines list?

[luke-hanwook]

          My question is : If `--ignore-engines` "fixes" the problem (i.e. it ignores the warning), why not pushing a new version of this module with adding Node 18 to the engine requirements? Is there _really_ an incompatibility, or is this message simply because v18 is missing from the engines list?

Because if there is really an incompatibility, then the solution is to downgrade to Node v16 until further notice. But if everything is fine, requiring to ignore the error (this issue was created many months ago already!) is not a proper solution.

Which is it?

Originally posted by @yanickrochon in nextauthjs/next-auth#4575 (comment)

[cbovard]

You nailed this on the head.