These are chat archives for AngularClass/angular2-webpack-starter

21st
Mar 2016
Aleš
@fxck
Mar 21 2016 17:50
so, with 4.0.0, what providers go here https://github.com/AngularClass/angular2-webpack-starter/blob/master/src/main.browser.ts only angular2’s, or 3rd party as well
it’s little confusing
Jamie Spittal
@Spittal
Mar 21 2016 19:27
I believe they are split up so you can have deps that are browser specific y’know things that inject DOM and window stuff
then there is the file that just bootstraps the stuff from the browser platform
but if you have providers for example a web worker you might want to bootstrap that with some other platform dependancies.
Aleš
@fxck
Mar 21 2016 19:51
yea, but I’m still not sure what belongs where, according to this https://github.com/AngularClass/angular2-webpack-starter/issues/454#issuecomment-199421596 only angular/vendor stuff belongs there
but
also I have some vendor providers that require some of my code(ngrx/store providerStore requires my reducers).. so where should that go?
Jamie Spittal
@Spittal
Mar 21 2016 20:10
Yeah fair enough actually… I’m having a little trouble knowing where to put my deps as well...
ryneflood
@ryneflood
Mar 21 2016 23:15
hey guys i'm running into a REALLY frustrating bug; it appears intermittently and seems to be random, as removing different parts of my app will fix it, but then then replacing the exact same code will work for a while, and then fail (what seems to be) randomly again
the same code also works fine when in a JSPM based build
This message was deleted
stacktrace
anyone around that can give me any suggestions on how to fix? started a week or so ago when I upgraded from around the beta.8 versions. In the mean time I've tried starting from a fresh copy of the starter, it'll work fine for a while but eventually it'll fail on that error. Sometimes it'll fail after just adding a new <div> to an HTML template
eventually the error is on this line: modules[moduleId].call(module.exports, module, module.exports, hotCreateRequire(moduleId));
ryneflood
@ryneflood
Mar 21 2016 23:48
i've turned off the "Hot Module Replacement" stuff; seemed to help for a minute (it worked first try after I turned it off). But then error is back after killing the server and restarting it
it errors out before it gets to any code in main.browser.ts so it seems likely that it has nothing to do with any angular code