Skip to content
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

modularize the webpack to meteor process #73

Open
jedwards1211 opened this issue Oct 5, 2015 · 2 comments
Open

modularize the webpack to meteor process #73

jedwards1211 opened this issue Oct 5, 2015 · 2 comments

Comments

@jedwards1211
Copy link
Owner

What I ultimately want is to be able to do the following:

require('shelljs/global');
var webpack2meteor = require('webpack2meteor');
var dirs = require('./dirs');
var serverConfig = require('./webpack/webpack.config.server.dev.js');
var clientConfig = require('./webpack/webpack.config.client.dev.js');

webpack2meteor(serverConfig, {meteor: dirs.meteor, target: 'server', mode: 'development'}, function(err) {
  if (err) return;
  webpack2meteor(clientConfig, {meteor: dirs.meteor, target: 'client', mode: 'development'}, function(err) {
    if (err) return;
    cd(dirs.meteor);
    exec('meteor', {async: true});
  });
});

This would make it possible to handle advanced Webpack use cases, especially code splitting, and allow users to get the latest improvements via the npm package rather than having to continually merge this skeleton project into their code.

@jedwards1211
Copy link
Owner Author

Actually now I'm thinking of using Webpack plugins to handle this, so that users can just put the plugin in their webpack configs and run Webpack however they want.

@jedwards1211
Copy link
Owner Author

Btw, my solution exists in the webpack-meteor-tools branch now. It's not quite ready for prime time but it basically works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant