Closed peter-jozsa closed 3 years ago
I've also added the warning message to README about the limitations of dynamic asset prefixes and statically generated pages.
I'm closing it since the PR #65 of @megazazik already contains this change plus he took care of the limitations related to statically generated pages.
This PR tries to make the usage of Dynamic Asset Prefix feature more clear. From now on if
dynamicAssetPrefix
field innext.config.js
is set totrue
we will always produce a dynamic url (based on theassetPrefix
extracted from Next.js runtime config) for imported images during transpilation. Unlike before we do not check during transpilation ifassetPrefix
field is defined or not in thenext.config.js
.