Seems there would be one more drawback. How to handle fs? about universal-webpack HOT 9 CLOSED

I don't understand what you are talking about.
Provide an example.

from universal-webpack.

The followings are server-side codes.

translations/index.js

import requireDir from 'require-directory';
export default requireDir(module); // This would be error if using bundled server.js, since it make use of fs to runtime load files.

getLocaleMessages.js

// get all translation message from build folder
import translations from './translations';

/**
 * Get all translated messages of a locale.
 * @param {string} locale - Locale.
 * @returns {{ locale: string, messages: Object }} - Object of locale and messages.
 */
function getLocaleMessages(locale) {
  const messages = translations[locale];
  return { locale, messages };
}

export default getLocaleMessages;

from universal-webpack.

So, what you're saying is that translations/index.js does bundle all the required modules on the client, but does not on the server?
If that's the case, then open the compiled server-side bundle, find the line where compiled translations/index.js goes, and post the compiled source of translations/index.js.

from universal-webpack.

No, it is not the case. Maybe i provide a more simple example.
fs.readFile(path.resolve(__dirname, .....));
After bundled, the __dirname is changed, the path would be incorrect, so cannot read the correct file.
I am thinking of setting something like this in start up
global.SERVER_SRC_PATH = '.....';
then change the above to
fs.readFile(SERVER_SRC_PATH, .....));

from universal-webpack.

So, you're saying that Webpack substitutes __dirname for client-side builds but doesn't do so for server-side builds?

from universal-webpack.

My client side would not run those codes. After webpack bundled, I found the server side __dirname always equal to '/', but it could be printed correctly in startup file which is not bundled by webpack.

from universal-webpack.

My client side would not run those codes.

Then you can move React rendering to a separate service and that would solve your issue
https://github.com/halt-hammerzeit/universal-webpack#separate-react-rendering-service-from-the-main-code

After webpack bundled, I found the server side __dirname always equal to '/'

Then that's what Webpack does for __dirname variable

from universal-webpack.

o.... My bad. Found solution by setting this option to webpack.
node: {
__dirname: true
}
webpack/webpack#1599

from universal-webpack.

(this workaround is now part of the library since several people requested it)
#30

from universal-webpack.