diff --git a/plugin/init_npm.js b/plugin/init_npm.js
index <HASH>..<HASH> 100644
--- a/plugin/init_npm.js
+++ b/plugin/init_npm.js
@@ -29,12 +29,6 @@ if(canProceed() && !fs.existsSync(npmContainerDir)) {
 
   // add new container as a package
   echo.sync("\nnpm-container", ">>", ".meteor/packages");
-
-  console.log();
-  console.log("-> npm support has been initialized.");
-  console.log("-> please start your app again.");
-  console.log();
-  process.exit(0);
 }
 
 // check whether is this `meteor test-packages` or not
Removed process.exit call

There's no need for the build process to stop after making the npm-container
directory. Meteor will automatically restart the build when it detects the
addition to .meteor/packages. I've tested that the declared npm modules in
package.json are brought in when running `meteor` in development and `meteor
build` for production