-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support custom moduleDirectories #195
Comments
I think so. I have to admit I don't really use this package except for @TrySound handled the 8.x release (huge refactoring). It seems there is some major issues tho like #168 so I may consider simply reverting to 7.x implementation (which is simpler and don't have this kind of bugs) since nobody is currently maintaining this package at the moment (and I found the current codebase more complicated, and API too low level). |
FWIW, this ended up being easy to work around for me, since apparently I was only using the moduleDirectories thing for a single directory. |
I would go for appending them. I guess nobody will want to remove those. |
Yeah, if they do, they can use |
Voicing my support for this. I'm using the application structure outlined by @ryanflorence, which relies on being able to customize In the meantime, I've just forked this repo and added the directory manually, which unblocks me until any official update. |
@neezer Thanks for chiming in. I want to get v9 shipped today or tomorrow; then this will be PR welcome for the next release. |
We ended up not using this pattern – the reason ended up being that we use CSS modules, for which modules directories support already works fine, and only used If you're using CSS modules, I'd recommend using https://github.com/css-modules/postcss-modules-values anyway. |
@RyanZim Awesome! Not sure if I'll have time to throw up a PR for this, but I'll see what I can do. |
Fixed in #256, released in v9.1.0. |
In 7.x, the specified
path
(s) functioned as additional module directories.I used this to follow the "huge apps" example in using nested
shared/
directories, that were resolved as module directories.Was there a specific reason for its removal? It's not a feature I've made heavy use of, but it seems like an odd removal. Is the idea that this feature is superseded by the custom
resolve
argument?The text was updated successfully, but these errors were encountered: