You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
What I ultimately want is to be able to do the following:
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.
The text was updated successfully, but these errors were encountered: