Version 2.16.0 of webpack-hot-middleware just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As webpack-hot-middleware is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 5.0.1 of react-redux just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As react-redux is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

== STR
$ brew install node
$ brew install yarn
$ git clone [email protected]:jcoreio/crater.git
$ cd crater
$ yarn

== FIXED WITH
$ brew uninstall node yarn
$ brew install --force node@6
$ brew link --force node@6
$ npm i

== Fresh install of OSX 2017-April-17

~/C/P/O/F/crater ❯❯❯ npm --version                                                                                    ⏎ master
4.2.0
~/C/P/O/F/crater ❯❯❯ node --version                                                                                     master
v7.9.0
~/C/P/O/F/crater ❯❯❯ yarn --version                                                                                     master
0.23.2

== ERROR log

gyp info using [email protected] | darwin | x64
gyp info spawn /usr/bin/python
gyp info spawn args [ '/usr/local/Cellar/yarn/0.23.2/libexec/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/Cellar/yarn/0.23.2/libexec/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/florian/.node-gyp/7.9.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/florian/.node-gyp/7.9.0',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/Cellar/yarn/0.23.2/libexec/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info ok
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
  CXX(target) Release/obj.target/debug/src/debug.o
../src/debug.cc:38:27: error: too few arguments to function call, expected at least 2, have 1
        v8::Debug::Call(fn);
        ~~~~~~~~~~~~~~~   ^
/Users/florian/.node-gyp/7.9.0/include/node/v8-debug.h:198:3: note: 'Call' declared here
  static MaybeLocal<Value> Call(Local<Context> context,
  ^
../src/debug.cc:46:61: error: too few arguments to function call, single argument 'isolate' was not specified
        Isolate* debug_isolate = v8::Debug::GetDebugContext()->GetIsolate();
                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/florian/.node-gyp/7.9.0/include/node/v8-debug.h:248:3: note: 'GetDebugContext' declared here
  static Local<Context> GetDebugContext(Isolate* isolate);
  ^
../src/debug.cc:61:67: error: too few arguments to function call, single argument 'isolate' was not specified
        Local<Context> debug_context = v8::Debug::GetDebugContext();
                                       ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/florian/.node-gyp/7.9.0/include/node/v8-debug.h:248:3: note: 'GetDebugContext' declared here
  static Local<Context> GetDebugContext(Isolate* isolate);
  ^
../src/debug.cc:66:54: error: too few arguments to function call, single argument 'isolate' was not specified
          debug_context = v8::Debug::GetDebugContext();
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/florian/.node-gyp/7.9.0/include/node/v8-debug.h:248:3: note: 'GetDebugContext' declared here
  static Local<Context> GetDebugContext(Isolate* isolate);
  ^
4 errors generated.
make: *** [Release/obj.target/debug/src/debug.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/Cellar/yarn/0.23.2/libexec/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:194:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Darwin 16.5.0
gyp ERR! command "/usr/local/Cellar/node/7.9.0/bin/node" "/usr/local/Cellar/yarn/0.23.2/libexec/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64/debug.node" "--module_name=debug" "--module_path=/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64"
gyp ERR! cwd /Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug
gyp ERR! node -v v7.9.0
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp build --fallback-to-build --module=/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64/debug.node --module_name=debug --module_path=/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:194:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:899:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
node-pre-gyp ERR! System Darwin 16.5.0
node-pre-gyp ERR! command "/usr/local/Cellar/node/7.9.0/bin/node" "/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug
node-pre-gyp ERR! node -v v7.9.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.32
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp build --fallback-to-build --module=/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64/debug.node --module_name=debug --module_path=/Users/florian/Code/Public/Opensource/Forks/jcoreio-crater/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64' (1)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Version 15.4.2 of react-dom just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As react-dom is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

I'm getting the following error when trying out the webpack2 branch (master branch works fine):

ERROR in multi main
Module not found: Error: Can't resolve 'babel' in '/Users/oscarconiel1/Sites/coniel/sis'
BREAKING CHANGE: It's no longer allowed to omit the '-loader' prefix when using loaders.
                 You need to specify 'babel-loader' instead of 'babel'.
 @ multi main

Hi again jcoreio,
Started off attempting the webpack2 branch which seems to be broken, the master branch seems to be solid though. I'm looking forward to trying out this repo.
~Falieson

=== Steps To Reproduce
$ git checkout webpack2
$ npm i && npm start

=== Error
~/Demos/crater (webpack2)

Use NoEmitOnErrorsPlugin instead.


ERROR in ./~/meteor-imports-webpack-plugin/meteor-config.json
Module parse failed: /Users/florian/Code/Education/Demos/crater/node_modules/json-string-loader/index.js?json={"meteorProgramsFolder":"/Users/florian/Code/Education/Demos/crater/build/meteor/bundle/programs","injectMeteorRuntimeConfig":false,"exclude":["autoupdate","global-imports","hot-code-push","reload","ecmascript"]}!/Users/florian/Code/Education/Demos/crater/node_modules/meteor-imports-webpack-plugin/meteor-config.json Unexpected token (1:114)
You may need an appropriate loader to handle this file type.
| module.exports = {"meteorProgramsFolder":"/Users/florian/Code/Education/Demos/crater/build/meteor/bundle/programs"
 @ ./~/meteor-imports-webpack-plugin/meteor-imports.js 2:13-44
 @ ./src/client/index.js
 @ multi ./src/client/index.js react-hot-loader/patch webpack-hot-middleware/client
^C

Is there a way to keep the framework code separate from the app code? (For example resolveModuleSource.js in src\server). This would make adding something like eslint a bit easier. It would also make it easier to modify the example app. Maybe have a \lib for framework code and a \src for application specific code?

Also (this may be a new issue), would it be possible to make the example a bit more modular? For example, be able to rip out SSR if it's not needed. I'd be happy enough if there was just a README file showing how to remove certain features.

I'm still figuring out how all the pieces work together but I'll see if I can contribute anything. (BTW, awesome skeleton. Exactly what I'm looking for!!)

If you have DISABLE_FULL_SSR enabled and you refresh the page (aka initial page load) the word "false" flashes briefly.

The reason is this code (line 25 Html.js):

    const root = PROD && !process.env.DISABLE_FULL_SSR && renderToString(
      <Provider store={store}>
        <RouterContext {...renderProps} />
      </Provider>
    )

I've replaced it with this:

    let root = renderToString(<div/>);
    if (PROD && !process.env.DISABLE_FULL_SSR) {
      const root = renderToString(
          <Provider store={store}>
            <RouterContext {...renderProps} />
          </Provider>
        )
    }

Version 2.4.0 of debug just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.12.0 of coveralls just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Should the redux-immutablejs NPM package be under dependencies instead of devDependencies?

I'm cloning a new repo:

git clone https://github.com/jcoreio/crater.git

Installing packages:

npm i

And running tests:

npm test

I'm getting the following error:

> [email protected] test /home/mike/dev/crater
> wdio wdio.conf.js

A service failed in the 'onPrepare' hook
Error: Exit code: null
    at ChildProcess.<anonymous> (/home/mike/dev/crater/node_modules/phantomjs-prebuilt/lib/phantomjs.js:117:18)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

Continue...

=======================================================================================
Selenium 2.0 / webdriver protocol bindings implementation with helper commands in nodejs.
For a complete list of commands, visit http://webdriver.io/api.html.
=======================================================================================

[15:29:39]  COMMAND     POST     "/wd/hub/session"
ERROR: Couldn't connect to selenium server
phantomjs
Error: Couldn't connect to selenium server

From #52: index.js is only compiled the build script (and docker script), not the prod script.

I've changed webapck/webpack.config.dev.js by adding the following resolve.alias:

const config = {
  context: root,
  devtool: 'eval',
  entry: [
    './src/client/index.js',
    'react-hot-loader/patch',
    'webpack-hot-middleware/client',
  ],
  resolve: {
    extensions: ['.js', '.jsx'],
    alias: {
      "client": root+"/src/client",
      "server": root+"/src/server",
      "universal": root+"/src/universal",
      "redux": root+"/src/universal/redux",
      "routes": root+"/src/universal/routes"
    }
  },

and when I build I get the error

ERROR in ./src/client/makeStore.js
Module not found: Error: Can't resolve 'redux' in '/Users/florian/Code/Public/PlanetX/planetx-boilerplate-crater/src/client'
 @ ./src/client/makeStore.js 7:13-29
 @ ./src/client/index.js
 @ multi ./src/client/index.js react-hot-loader/patch webpack-hot-middleware/client

ERROR in ./~/react-redux/es/connect/mapDispatchToProps.js
Module not found: Error: Can't resolve 'redux' in '/Users/florian/Code/Public/PlanetX/planetx-boilerplate-crater/node_modules/react-redux/es/connect'
 @ ./~/react-redux/es/connect/mapDispatchToProps.js 1:0-43

no other changes - any ideas here?

btw @jedwards1211 do you want to be in touch over skype/gtalk? my address is [email protected]

This is a bit of an odd error. I made a layout component that renders a bit of markup and then this.props.children and added some CSS markup in a separate .css file. I add it to the root route at src/universal/routes/index.js like this:

return {
  component: Layout,
  childRoutes: [
    require('./home').default(store),
  ]
}

When I try to run in dev mode I get this error:

SyntaxError: /home/mike/dev/crater/src/universal/components/Header.css: Unexpected token (1:0)
> 1 | .header {
    | ^
  2 |   background-color: mediumpurple;
  3 | }
  4 | 
    at Parser.pp.raise (/home/mike/dev/crater/node_modules/babylon/lib/parser/location.js:22:13)
    at Parser.pp.unexpected (/home/mike/dev/crater/node_modules/babylon/lib/parser/util.js:91:8)
    at Parser.pp.parseExprAtom (/home/mike/dev/crater/node_modules/babylon/lib/parser/expression.js:512:12)
    at Parser.parseExprAtom (/home/mike/dev/crater/node_modules/babylon/lib/plugins/jsx/index.js:16:22)
    at Parser.pp.parseExprSubscripts (/home/mike/dev/crater/node_modules/babylon/lib/parser/expression.js:270:19)
    at Parser.pp.parseMaybeUnary (/home/mike/dev/crater/node_modules/babylon/lib/parser/expression.js:250:19)
    at Parser.pp.parseExprOps (/home/mike/dev/crater/node_modules/babylon/lib/parser/expression.js:180:19)
    at Parser.pp.parseMaybeConditional (/home/mike/dev/crater/node_modules/babylon/lib/parser/expression.js:157:19)
    at Parser.pp.parseMaybeAssign (/home/mike/dev/crater/node_modules/babylon/lib/parser/expression.js:120:19)
    at Parser.parseMaybeAssign (/home/mike/dev/crater/node_modules/babylon/lib/plugins/flow.js:447:20)

I have a repro here: https://github.com/koretech/crater/tree/router-component-css-error

If you comment out the CSS imports it works fine.

If I get rid of the component: Layout line in the route file and instead wrap what's in App.js with <Layout></Layout> it works fine. You can see the CSS and component working fine here: https://github.com/koretech/crater/tree/router-component-css-alternative.

It almost seems like this is a webpack or babel issue but I can't seem to pin it down.

Version 2.30.4 of eslint-plugin-flowtype just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-flowtype is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

@jedwards1211 How would you recommend handling static assets in development and production with this setup?

I am porting my meteor app to this architecture and I have an existing folder full of assorted images which were previously served up by meteor in the public folder. It looks like I could use https://github.com/webpack/file-loader which would require some refactoring or I could add a route to server/index.js. I am not sure what is the best course of action or if I am missing a better way of doing it.

Fresh git clone.

Getting warnings like:

Warning: You are manually calling a React.PropTypes validation function for the `store` prop on `Html`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `title` prop on `Html`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `assets` prop on `Html`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `env` prop on `Html`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `settings` prop on `Html`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `renderProps` prop on `Html`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.

Is there a way to mitigate these warnings or are they stemming from a 3rd-party library?

In #61 @darkadept asked how to turn off SSR (i.e. only render the basic <html> shell and do everything else on the client). It's not completely trivial, so I'll be making a PR in a moment

Add react-meteor-data plugin to meteor and react-addons-pure-render-mixing to package.json and the following happens on the client if you try to import from meteor/react-meteor-data:

WARNING: npm peer requirements (for react-meteor-data) not installed:
 - [email protected] not installed.
 - [email protected] not installed.

Read more about installing npm peer dependencies:
  http://guide.meteor.com/using-packages.html#peer-npm-dependencies


modules-runtime.js:128 Uncaught Error: Cannot find module 'react'
require.resolve @   modules-runtime.js:128
Module.resolve  @   modules-runtime.js:84
Mp.import   @   modules.js:282
meteorInstall.node_modules.meteor.react-meteor-data.createContainer.jsx @   react-meteor-data.js:243
fileEvaluate    @   modules-runtime.js:180
require @   modules-runtime.js:109
meteorInstall.node_modules.meteor.react-meteor-data.react-meteor-data.jsx   @   react-meteor-data.js:45
fileEvaluate    @   modules-runtime.js:180
require @   modules-runtime.js:109
(anonymous function)    @   react-meteor-data.js:299
(anonymous function)    @   react-meteor-data.js:310
(anonymous function)    @   app.js:2098
__webpack_require__ @   app.js:556
fn  @   app.js:87
webpackContext  @   packages_nonrecursive_\.js$:33
(anonymous function)    @   meteor-imports.js:18
(anonymous function)    @   meteor-imports.js:16
(anonymous function)    @   app.js:3178
__webpack_require__ @   app.js:556
fn  @   app.js:87
(anonymous function)    @   index.js:3
(anonymous function)    @   app.js:2524
__webpack_require__ @   app.js:556
fn  @   app.js:87
(anonymous function)    @   multi_main:1
(anonymous function)    @   app.js:586
__webpack_require__ @   app.js:556
(anonymous function)    @   app.js:579
(anonymous function)    @   app.js:582

Looks like meteor packages can't resolve npm packages. I'm not sure how to fix this.

I've been having strange issues with crater server-side. I've been getting 100% usage on a single node process. I was pretty sure that it had something to do with the accounts-base meteor package.

I cloned a fresh crater, edited meteor/.meteor/packages and added accounts-base, ran npm install and npm start. I watched my cpu usage and it was normal until I loaded the page. Then one of my cpu cores went to 100%. It was the node process. It continues running at 100% even if I close the client web browser.

If I run npm run debug I can record a JavaScript CPU profile and I can see that a Promise gets called over and over and over. Remember, this is without changing any code, just added the accounts-base package.

Now the stupid part is I just tried again and now it's not doing it anymore. At least with my fresh crater clone. It's still doing it consistently in my crater-based app. I did have the problem in a fresh crater clone too though, just not consistent.

In my crater-based app it's running at 100% cpu even in production mode too.

Edit: more details:
Node v6.3.1
Npm v3.10.3
O/S: Ubuntu 16.10

First, thanks a bunch for making this repo! Its everything I've been looking for (including Flow!).

I've tried on 2 different macbooks, so I don't think its anything local. I've cloned, and first tried the webpack2 branch and then once I got an error I switched back to master. This is the error I get when running npm start on master.

ERROR in ./~/meteor-imports-webpack-plugin/meteor-config.json
Module parse failed: ~/crater/node_modules/json-string-loader/index.js?json={"meteorProgramsFolder":~/crater/build/meteor/bundle/programs","injectMeteorRuntimeConfig":false,"exclude":["autoupdate","global-imports","hot-code-push","reload","ecmascript"]}!~/crater/node_modules/meteor-imports-webpack-plugin/meteor-config.json Unexpected token (1:114)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (1:114)

This warning is printed from the version of loader-utils used by postcss-loader. It will eventually be fixed; just created this issue so people would know they can ignore it.

> babel-node scripts/prod.js

meteor/node_modules is up to date
build/meteor is up to date
Meteor npm dependencies are up to date
Happy[1]: Version: 3.0.3. Using cache? no. Threads: 4
Happy[1]: Version: 3.0.3. Using cache? no. Threads: 4
Happy[1]: All set; signalling webpack to proceed.
Happy[1]: All set; signalling webpack to proceed.
(node:91523) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.

Version 6.4.1 of babel-loader just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.3.0 of postcss-loader just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As postcss-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

windows10+cmd
webpack built b8de0552b7a84df74e4c in 2635ms
[smart-restart] can't execute file: F:\web\xiaolu\meteor\crater\src\index.js
[smart-restart] error given was: MongoError: failed to connect to server [localhost:27017] on first connect
at Object.Future.wait (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\node_modules\fibers\future.js:449:15)
at new MongoConnection (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\packages\meteor:\�app\packages\mongo\mongo_driver.js:219:27)
at new MongoInternals.RemoteCollectionDriver (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\packages\meteor:\�app\packages\mongo\remote_collection_driver.js:4:16)
at Object. (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\packages\meteor:\�app\packages\mongo\remote_collection_driver.js:38:10)
at Object.defaultRemoteCollectionDriver (packages\underscore.js:784:19)
at new Mongo.Collection (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\packages\meteor:\�app\packages\mongo\collection.js:103:40)
at Object. (F:/web/xiaolu/meteor/crater/src/universal/collections/Counts.js:6:16)
at Module._compile (module.js:541:32)
at loader (F:\web\xiaolu\meteor\crater\node_modules\babel-register\lib\node.js:144:5)
at Object.require.extensions.(anonymous function) [as .js] (F:\web\xiaolu\meteor\crater\node_modules\babel-register\lib\node.js:154:7)
- - - - -
at . (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\npm\node_modules\meteor\npm-mongo\node_modules\mongodb-core\lib\topologies\server.js:313:35)
at emitOne (events.js:96:13)
at emit (events.js:188:7)
at . (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\npm\node_modules\meteor\npm-mongo\node_modules\mongodb-core\lib\connection\pool.js:271:12)
at g (events.js:286:16)
at emitTwo (events.js:106:13)
at emit (events.js:191:7)
at Socket. (F:\web\xiaolu\meteor\crater\build\meteor\bundle\programs\server\npm\node_modules\meteor\npm-mongo\node_modules\mongodb-core\lib\connection\connection.js:165:49)
at Socket.g (events.js:286:16)
at emitOne (events.js:96:13)
[smart-restart] further repeats of this error will be suppressed...

I'm wondering if it's possible (and useful) to also use webpack for the server files in development.
This would add the possibility of using TS-Loaders for language support and other things.

I'm especially interested in getting crater to work with Typescript.
This works fine for client code but I'm struggling in getting this to work for server code as well.

Has anyone got this working and is it worth the effort?
I'm worried that bundling server code for webpack might result in poor build performance (many small modules vs. 1 huge bundle...).

Despite performance - are there other reasons for skipping webpack for server in dev?

Reverse proxying is a waste of computation, I wasn't aware of rawConnectHandlers until now

  // Packages and apps can add handlers that run before any other Meteor                                             //
  // handlers via WebApp.rawConnectHandlers.                                                                         //
  var rawConnectHandlers = connect();                                                                                // 596
  app.use(rawConnectHandlers);  

There seem to be a few issues:

• happypack does not work with webpack beta > 22 amireh/happypack#91
• postcss has to be configured with webpack.LoaderOptionsPlugin

new webpack.LoaderOptionsPlugin({
    options: {
        postcss: [cssModulesValues]
    }
}),

• css-loader version needs to be bumped to 0.25.0

After these changes it seems to run OK, but I am very new to webpack so there may still be other issues.

It doesn't work to dispatch thunk actions in production SSR. The following error occurs:

Error: Actions must be plain objects. Use custom middleware for async actions..

From what I can tell it's because the makeStore.js is never called in production SSR (createSSR.js). The store is created with:
const store = createStore(makeReducer(), iMap())
Middlewares are not applied during SSR.

Version 1.2.0 of pre-commit just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As pre-commit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.9.0 of redux-logger just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As redux-logger is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Getting this error in the browser console in a fresh-from-git version: "app.js:1 Uncaught SyntaxError: Unexpected token <".

== STR

• When running npm run start
• and a successful webpack build
• in a browser go to localhost:4000

webpack server terminal receives output

Warning: You are manually calling a React.PropTypes validation function for the `__meteor_runtime_config__` prop on `Html`. This is deprecated and will throw in the standalone `prop-types` package. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `store` prop on `Html`. This is deprecated and will throw in the standalone `prop-types` package. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `title` prop on `Html`. This is deprecated and will throw in the standalone `prop-types` package. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
Warning: You are manually calling a React.PropTypes validation function for the `assets` prop on `Html`. This is deprecated and will throw in the standalone `prop-types` package. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.

@jedwards1211 I'll probably submit a PR for this in the next day or two

How to upgrade [email protected]

First I wanted to thank you for this great package, its exactly what meteor needs ..

Regarding my Issue
I have a react router configuration like this and want to use the kind of difference between the app containers in the redux router. Its working if i replace the Router, but then the HMR is gone.

  <Route path="/" component={App}>
    <IndexRoute component={LoginPage} />
      <Route path="login" component={LoginPage} />
      </Route>
      <Route path="/secure" component={AuthenticatedApp}>
        {/* Authentication-protected routes go here */}
          <IndexRoute component={ContactsPage} />
          <Route path="configuration">
            <IndexRoute component={UserConf} />
            <Route path="usersettings" component={UserConf} />
            <Route path="contactssettings" component={ContactsConf} />
            <Route path="*" component={NotFoundPage} />
          </Route>
          <Route path="contacts" component={ContactsPage} />
          <Route path="*" component={NotFoundPage} />
        </Route>
    <Route path="*" component={NotFoundPage} />

I tried to put it in the store objects like this:

export default (store: Store): Object => ({
  path: '/secure',
  component: AuthenticatedApp,
  indexRoute: {
    component: ContactsPage,
  },
})

but then its not using the first main app container anymore, instead shows only the child component that should be rendered in the container.

How can i define the children for specific routes in the store object?

Thank you for your help.

So I've discovered a bug where webpack isn't liking a require'd json file from a dependent npm package. This is in dev-mode and the error is this:

ERROR in ./~/entities/maps/legacy.json
Module parse failed: /home/mike/dev/crater/node_modules/entities/maps/legacy.json Unexpected token (1:9)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (1:9)
    at Parser.pp$4.raise (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:2221:15)
    at Parser.pp.unexpected (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:603:10)
    at Parser.pp.semicolon (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:966:10)
    at Parser.pp$1.parseStatement (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:730:24)
    at Parser.pp$1.parseBlock (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:981:25)
    at Parser.pp$1.parseStatement (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:638:25)
    at Parser.parse (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:516:17)
    at Object.parse (/home/mike/dev/crater/node_modules/webpack/node_modules/acorn/dist/acorn.js:3098:39)
 @ ./~/entities/lib/decode.js 2:16-46

To reproduce this I just included the react-markdown package:
npm install --save react-markdown

And then included it in the App.js component:
import Markdown from 'react-markdown'
...
<Markdown source="This is a test"/>

If you edit the node_modules/entities/lib/*.js files and add the json! prefix to the require statements: require("json!../maps/entities.json") then webpack compiles properly.

Is this a webpack configuration issue or a problem with the entities npm module?

It's 2016, and your Meteor app has crash landed in ...

This describes my situation perfectly!

What do you see the pros/cons of using crater vs using meteor-webpack & meteor-react-router-ssr?

How can i see server logs (e.g. console.log from server.js) ?

Thanks
java99

Version 3.16.1 of eslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Is it possible to use tree shaking with webpack2 in this skeleton?

On the webpack2 branch I changed my .babelrc to the following

{
  "presets": [ ["es2015", { "loose": true, "modules": false}], "stage-1", "react", "flow"],
  "plugins": [
    "transform-runtime",
    "meteor-imports"
  ]
}

Which as I understand it causes babel to no longer process imports because we want webpack to do it. This breaks the start script however. Changing the package.json scripts entry to

"start": "babel-node --presets es2015,flow scripts/start.js",

Allows the webpack build to start, but running the server fails with

[smart-restart] error given was: SyntaxError: Unexpected reserved word

I am not really familiar with how smart-restart works. Is it possible to build with modules: false in babel to have webpack2 do tree shaking? This could massively reduce the bundle size on a lot of applications if it can be made to work.

I was using this project for some time and it worked great until yesterday.

After adding 'accout-facebook' via atmosphere, the app stopped working. After launch few errors come up in the console:

Cannot read property 'Reload' of undefined - refers to oauth package like this:

//(...)    
/* Imports */
var Meteor = Package.meteor.Meteor;
var global = Package.meteor.global;
var meteorEnv = Package.meteor.meteorEnv;
var check = Package.check.check;
var Match = Package.check.Match;
var _ = Package.underscore._;
var Reload = Package.reload.Reload; //<==== error here
var Base64 = Package.base64.Base64;
var URL = Package.url.URL;
//(...)

and

Cannot read property 'ServiceConfiguration' of undefined in accounts-base packege.

It's worth mentioning, that i have been sucessfully using the accounts-base package before the installation.

I tried to analyze the Webpack compiled app.js, and it seems that there is no Package.reload included in there.

Can you somehow point me towards the right direction of solving this problem?

When running in dev mode, does the meteor database also run?

I'm assuming you need to have your own database configured? Also, how does one go about connecting meteor to the database? It might be a good addition to the README.

@jedwards1211 go ahead and close this, posting for anyone else searching the issues

STR

$ git clone [email protected]:jcoreio/crater.git
$ cd crater
$ npm run start

Fixed by

going to https://www.meteor.com/install
the issue is not having meteor installed

Error-log - you'll get an error like this

~/C/P/O/F/crater ❯❯❯ npm run start                                                                                      master

> [email protected] start /Users/falieson/Code/jcoreio-crater
> babel-node scripts/start.js

installing meteor/node_modules...
meteor@ /Users/falieson/Code/jcoreio-crater/meteor
└─┬ [email protected]
  ├── [email protected]
  └── [email protected]

npm WARN meteor@ No description
npm WARN meteor@ No repository field.
npm WARN meteor@ No license field.
building Meteor packages...
Error: spawn meteor ENOENT
    at exports._errnoException (util.js:1050:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:367:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickDomainCallback (internal/process/next_tick.js:128:9)

The message Ignoring duplicate publish: 'counts' shows up in the console in prod mode because separate copies of collections/Counts are loaded, one in the usual location, one bundled into prerender.js. I need to figure out a solution for this

Version 1.2.1 of pre-commit just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As pre-commit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Following the instructions in the README gives me this error when running npm start:

This was on Node v0.11.16 with v2.3.0. I also tried with Node v6.3.0 and got the same error.

mike@THRPC-028:~/dev/crater_debug$ npm start

> [email protected] start /home/mike/dev/crater_debug
> NODE_ENV=development node src/server/index.js

/home/mike/.meteor/packages/meteor-tool/.1.4.1_1.183vrcm++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/fibers.js:16
        throw new Error('`'+ modPath+ '.node` is missing. Try reinstalling `node-fibe
              ^
Error: `/home/mike/.meteor/packages/meteor-tool/.1.4.1_1.183vrcm++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/bin/linux-x64-v8-3.28/fibers.node` is missing. Try reinstalling `node-fibers`?
    at Object.<anonymous> (/home/mike/.meteor/packages/meteor-tool/.1.4.1_1.183vrcm++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/fibers.js:16:8)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/mike/dev/crater_debug/meteor/.meteor/local/build/programs/server/boot.js:1:75)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)

I'm trying to use a component that is trying to use the global window object (google-maps-react). In dev mode it works fine, but in prod mode the server webpack config has trouble. Obviously window is not defined on the server.

How does one use these kind of components with SSR?

F:\web\xiaolu\meteor\a031\a031_semantic\crater>npm -v
3.8.9
F:\web\xiaolu\meteor\a031\a031_semantic\crater>node -v
v6.2.1
meteor update
npm start
windows10
BUG：
F:\web\xiaolu\meteor\a031\a031_semantic\crater>npm start

[email protected] start F:\web\xiaolu\meteor\a031\a031_semantic\crater
NODE_ENV=development node src/server/index.js

'NODE_ENV' 不是内部或外部命令，也不是可运行的程序
或批处理文件。

npm ERR! Windows_NT 10.0.10240
npm ERR! argv "E:\Program Files\nodejs\node.exe" "E:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v6.2.1
npm ERR! npm v3.8.9
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: NODE_ENV=development node src/server/index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'NODE_ENV=development node src/server/index.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the crater package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! NODE_ENV=development node src/server/index.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs crater
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls crater
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! F:\web\xiaolu\meteor\a031\a031_semantic\crater\npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'E:\Program Files\nodejs\node.exe',
1 verbose cli 'E:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 silly lifecycle [email protected]prestart: no script for prestart, continuing
7 info lifecycle [email protected]start: [email protected]
8 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]start: PATH: E:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;F:\web\xiaolu\meteor\a031\a031_semantic\crater\node_modules.bin;E:\Program Files\nodejs;C:\Program Files (x86)\Common Files\NetSarang;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;E:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;E:\Program Files\AOMEI Backupper 2.1;F:\web\UPUPW_K2.0_64\PHPX\PHP70;C:\ProgramData\ComposerSetup\bin;E:\Program Files\nodejs;E:\Program Files\Git\cmd;E:\Program Files\Python27;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;E:\Program Files\TortoiseGit\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Users\xiaolu\AppData\Roaming\Composer\vendor\bin;C:\Users\xiaolu\AppData\Roaming\npm;C:\Users\xiaolu\AppData\Local.meteor
10 verbose lifecycle [email protected]start: CWD: F:\web\xiaolu\meteor\a031\a031_semantic\crater
11 silly lifecycle [email protected]start: Args: [ '/d /s /c', 'NODE_ENV=development node src/server/index.js' ]
12 silly lifecycle [email protected]start: Returned: code: 1 signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: NODE_ENV=development node src/server/index.js
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (E:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:245:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (E:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:852:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid [email protected]
16 verbose cwd F:\web\xiaolu\meteor\a031\a031_semantic\crater
17 error Windows_NT 10.0.10240
18 error argv "E:\Program Files\nodejs\node.exe" "E:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
19 error node v6.2.1
20 error npm v3.8.9
21 error code ELIFECYCLE
22 error [email protected] start: NODE_ENV=development node src/server/index.js
22 error Exit status 1
23 error Failed at the [email protected] start script 'NODE_ENV=development node src/server/index.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the crater package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error NODE_ENV=development node src/server/index.js
23 error You can get information on how to open an issue for this project with:
23 error npm bugs crater
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls crater
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

My app is :meteor 1.4.1+react
My original frame for this：
https://github.com/thereactivestack/kickstart-meteor-react-router
I want you to try this!