-
Notifications
You must be signed in to change notification settings - Fork 48
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
does not write webpack-assets.json to location specified as rootDir #30
Comments
|
how would i configure where that gets written to? |
you can use the configuration: |
thanks. i got it to work by specifying a note though: at that link it says in your comments above that it would default to writing webpack-assets.json the webpack configuration context, which i am setting to my |
Well, it did create |
without the additional configuration change to |
can you post your |
here's my fork and branch i'm working from: https://github.com/bdefore/react-redux-universal-hot-example/tree/parameterized-routes-and-source-path you should be able to test either case if you add/remove the line here https://github.com/bdefore/react-redux-universal-hot-example/blob/parameterized-routes-and-source-path/external/webpack-overrides-config.js#L8 |
ok |
Following the example here: https://github.com/erikras/react-redux-universal-hot-example/blob/master/bin/server.js#L4 I'm attempting to change
rootDir
to another path, in order to better externalize my source from the boilerplate code. For example, I'd like to change that tovar rootDir = path.resolve(__dirname, '../external');
I also then update thecontext
to point to the same path, so that the tools can find thewebpack-assets.json
.Unfortunately, what I see is that it is writing the file into the project root, rather than what I'm specifying.
If I add logs to here: https://github.com/halt-hammerzeit/webpack-isomorphic-tools/blob/master/source/index.js#L149
I get the following output:
But then
webpack-assets.json
is written to the project root and it never finds them, so I see endless logs like the following:I'm running version 2.2.18
The text was updated successfully, but these errors were encountered: