-
Notifications
You must be signed in to change notification settings - Fork 5
Doesn't resolve LESS imports that have no extension #6
Comments
Do we really have an alias in Kibana that resolves less files without the need for |
Apparently so. I've been using it, which is how I found this issue 😛 But I'm totally fine with using the workaround for a long-term solution. |
Realized the way I worded the issue title was confusing. I retitled it |
@spalger how would you feel about removing that resolution rule in Kibana core, maybe as part of 6.0.0? I don't know if you have an idea of how much code relies on it, I can take a look if you don't know offhand. |
@tsullivan is it possible that that import was just |
Just wondering.. we are sure that webpack is importing the less file sans extension? |
It's due to I agree it should be removed. Honestly, the whole setting seems like an anti-pattern. |
I say rip it out and let plugins update to fix it. No need to wait for 6.0. I don't think it's a pattern we should have supported in the first place, and webpack will complain immediately when it can't resolve the file |
Are you proposing ripping this out for |
I am proposing removing the resolution for |
Fixed by #15 |
If an import statement points to a LESS file with no extension, webpack knows how to import it, but the glob pattern builder is specific to JS files.
A workaround is just to add the
.less
extension in the import, which may actually be a better way to do it, for clarity.Doesn't work:
Works:
The text was updated successfully, but these errors were encountered: