[RFC] Remove next/asset as it's undocumented
#5970
Comments
timneutkens
changed the title
next/asset as it's undocumented / not really usefulnext/asset as it's undocumented
Merged
timneutkens
added a commit
that referenced
this issue
Jan 14, 2019
* Remove next/asset Reasoning described in #5970 * Remove next/asset tests * Bring back asset-page
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature request
Is your feature request related to a problem? Please describe.
Currently there is a
next/assetmodule that isn't in use anywhere. It's main purpose is to prefix/staticwith theassetPrefix, it only works for/static, so it doesn't really expose theassetPrefixfor usage.Describe the solution you'd like
Removes this module to reduce API surface. It's currently being bundled even when not used because we have to instantiate the module.
Describe alternatives you've considered
I currently don't see a valid use-case for this API. I'm pretty confident we can remove it, it was never documented in the readme, it's not in use in zeit.co / nextjs.org and I reached out to a few users to see if they used it, which was not the case, because it was never documented and doesn't serve a wealth of use cases.
The text was updated successfully, but these errors were encountered: