-
Notifications
You must be signed in to change notification settings - Fork 243
[FAQ] Specifying an import root to avoid relative import paths #318
Comments
+1 already doing this in my setup. |
As a reference, see the discussion in #203 - which doesn't mean this can't be done :) |
Perhaps a simple configuration variable so that it can be done outside of modifying the factory for devs? Not too hard for most of us to add it but for new devs it would likely be appealing and those that don't want it can simply turn it off. I did that with aliases so I could just define a webpack_aliases: {} in the config using
|
as per #203 concern with IDE is fairly trivial. at least in WebStorm you can simply mark |
Like @codepunkt said in #203: Wasn't aware of this discussion. |
It's a common enough request that perhaps we should put something like @bradennapier's suggestion into the FAQ section? |
@ctrlplusb Thats a good idea :). |
Hello,
Maybe its a good idea to add this line to the webpack resolve module:
modules: ['src/shared','node_modules'],
So you are able to import your components like this:
import Navbar from 'components/Navbar'
The text was updated successfully, but these errors were encountered: