Popular posts

Would you have any article or repo with that implementation to get a feel of the setup!?

@antoinegrant You can write a simple gulp task like following to precompile your files :

gulp.task('babelify',function(){
    return gulp.src(['src/**/*.js']).pipe(babel({presets: ['es2015']})).pipe(gulp.dest('build/src'));
});

Then you can directly require the compiled modules without registering babel in production.

Ditto, I tend to always create bundles. As few as possible, but enough to still be able to load in less frequently used things.

@sandeep I totally approve of the solution in your comment above, to compile your src to a dist folder using babel. But one thing to keep in mind here is that this approach does not create a 'bundle' using webpack, rather it compiles individual files.

So if I add a criteria to my question, to pass each file thru webpack loader so that we can start using css-module, for example, on the server side.

1. Would using something like css-modules-require-hook with babel-register make sense?
2. Or would it make more sense to create a server specific bundle with webpack? If so, what would the architecture look like?

@antoinegrant The webpack team is doing a live AMA on Hashnode now. Why not ask this question in the Q&A page?