Closed ctrlaltdylan closed 3 years ago
Can you elaborate on the problem you're facing with sharp
. Webpack doesn't have a root extensions
property. Instead, the only extensions property it has resides within resolve, which deals with resolving imports without an explicit extension:
So instead of this:
import file from "dir/path/to/file.ext"
You can do this:
import file from "dir/path/to/file";
Therefore, I'm not sure how this will be able to apply to your goal:
ignore the sharp library
Typical webpack configs (for development)
Describe the feature you'd like to request
Currently it appears that under the hood the Webpack
extensions
entry is a function.This makes is difficult to extend to add your own definition. For example, I'm trying to add an extension object to ignore the
sharp
library.However, because the
webpack.config.extensions
is a function, it's not clear how to extend it.Describe the solution you'd like
Documentation on a workaround would be enough. I don't think most NextJS users are trying to change webpack configs too deeply.
Perhaps something like this?
Describe alternatives you've considered
Tried the above, no luck. I'll need to dive in the source more to find out what's going on but haven't had the chance yet.