{"action":"created","issue":{"url":"https://api.github.com/repos/ipselon/structor/issues/44","repository_url":"https://api.github.com/repos/ipselon/structor","labels_url":"https://api.github.com/repos/ipselon/structor/issues/44/labels{/name}","comments_url":"https://api.github.com/repos/ipselon/structor/issues/44/comments","events_url":"https://api.github.com/repos/ipselon/structor/issues/44/events","html_url":"https://github.com/ipselon/structor/issues/44","id":131511600,"number":44,"title":"External code tree, expose Structor's internal WebPack configs?","user":{"login":"radman-x","id":9258904,"avatar_url":"https://avatars.githubusercontent.com/u/9258904?v=3","gravatar_id":"","url":"https://api.github.com/users/radman-x","html_url":"https://github.com/radman-x","followers_url":"https://api.github.com/users/radman-x/followers","following_url":"https://api.github.com/users/radman-x/following{/other_user}","gists_url":"https://api.github.com/users/radman-x/gists{/gist_id}","starred_url":"https://api.github.com/users/radman-x/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/radman-x/subscriptions","organizations_url":"https://api.github.com/users/radman-x/orgs","repos_url":"https://api.github.com/users/radman-x/repos","events_url":"https://api.github.com/users/radman-x/events{/privacy}","received_events_url":"https://api.github.com/users/radman-x/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-05T00:01:53Z","updated_at":"2016-02-05T06:47:37Z","closed_at":null,"body":"We have been experimenting with Structor a lot over the last few weeks and it continues to look very promising. However,  we need a way to access a large external source code tree whose dependency tree we cannot modify by putting it under Structor's /src/client/components, etc. Also, because of its size, we cannot add everything into Structor's index.js file, like you suggest in the documentation.\r\n\r\nNormally, we just modify WebPack's config file and include resolve.root or resolve.moduleDirectories and this does work when we build with Structor's webpack-config.js (which we modify for this).\r\n\r\nHowever, when editing, Structor runs an internal, programmatic invocation of WebPack that we have no access to so we cannot set these configuration properties.\r\n\r\nDo you have any suggestions for how to handle this? Does it make sense to expose the internal WebPack configs (or at least the resolve.root/moduleDirectories)?"},"comment":{"url":"https://api.github.com/repos/ipselon/structor/issues/comments/180225970","html_url":"https://github.com/ipselon/structor/issues/44#issuecomment-180225970","issue_url":"https://api.github.com/repos/ipselon/structor/issues/44","id":180225970,"user":{"login":"ipselon","id":11865795,"avatar_url":"https://avatars.githubusercontent.com/u/11865795?v=3","gravatar_id":"","url":"https://api.github.com/users/ipselon","html_url":"https://github.com/ipselon","followers_url":"https://api.github.com/users/ipselon/followers","following_url":"https://api.github.com/users/ipselon/following{/other_user}","gists_url":"https://api.github.com/users/ipselon/gists{/gist_id}","starred_url":"https://api.github.com/users/ipselon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ipselon/subscriptions","organizations_url":"https://api.github.com/users/ipselon/orgs","repos_url":"https://api.github.com/users/ipselon/repos","events_url":"https://api.github.com/users/ipselon/events{/privacy}","received_events_url":"https://api.github.com/users/ipselon/received_events","type":"User","site_admin":false},"created_at":"2016-02-05T06:47:37Z","updated_at":"2016-02-05T06:47:37Z","body":"@radman-x try to include your configuration into `.stuctor/webpack.config.js`. \r\n\r\nOtherwise you may fork this repo and change `src/server/src/MiddlewareCompilerManager.js` as you need.\r\n\r\nHow large is your component tree?\r\n"}}