prevent "loading" is ignored by next/dynamic because you have enabled "suspense" warning, when loading is undefined

[hacknlove]

fixes #40388

This issue is marked as fixed, but unless I set specifically loading: null I am still getting the warning

"loading" is ignored by next/dynamic because you have enabled "suspense". Place your loading element in your suspense boundary's "fallback" prop instead. Read more: https://nextjs.org/docs/messages/invalid-dynamic-suspense

Not set any loading, (so loading is undefined) should not cause this warning.

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have a helpful link attached, see contributing.md

Feature

• Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• Integration tests added
• Documentation added
• Telemetry added. In case of a feature if it's used or not.
• Errors have a helpful link attached, see contributing.md

Documentation / Examples

• Make sure the linting passes by running pnpm lint
• The "examples guidelines" are followed from our contributing doc

[SukkaW]

[hacknlove]

Oh. I see what's going on.

We are setting a default loadableOptions.loading so when the user enables the suspense mode we need to unset the default.

It's not a critical bug, but developer experience matters, and people freak out with warnings with unknown origin.

I have updated the PR.
I should have given it a more profound look, in the first place, instead of wasting your time.

Thanks for your revision.