Open devonsams opened 7 years ago
I'm seeing in my build that this section is getting jumbled up. I'm still trying to figure out why though:
var __WEBPACK_IMPORTED_MODULE_0__angular_core__ = __webpack_require__(1),
__WEBPACK_IMPORTED_MODULE_1_rxjs_ReplaySubject__ = (__webpack_require__.n(__WEBPACK_IMPORTED_MODULE_0__angular_core__), __webpack_require__(19)),
__WEBPACK_IMPORTED_MODULE_2__angular_common__ = (__webpack_require__.n(__WEBPACK_IMPORTED_MODULE_1_rxjs_ReplaySubject__), __webpack_require__(3)),
__WEBPACK_IMPORTED_MODULE_3__angular_router__ = (__webpack_require__.n(__WEBPACK_IMPORTED_MODULE_2__angular_common__), __webpack_require__(5)),
__WEBPACK_IMPORTED_MODULE_4_rxjs_add_operator_filter__ = (__webpack_require__.n(__WEBPACK_IMPORTED_MODULE_3__angular_router__), __webpack_require__(20));
__webpack_require__.n(__WEBPACK_IMPORTED_MODULE_4_rxjs_add_operator_filter__);
__webpack_require__.d(__webpack_exports__, "a", function() {
return Angulartics2
});
edit: this isn't the problem.
I was using systemjs-builder 0.16.9 and downgraded to 0.15.34 and it fixed the problem. It might have something to do with this open issue: https://github.com/systemjs/systemjs/issues/1587
I can confirm this. There seems to be real issues when using SystemJS 0.20.x . I have pushed a very minimal seed-project with angulartics here:
https://github.com/ZuSe/angular2-seed/tree/test/angulartics2
But i only run into the issue when compiling aot.
I think there was some issues with older version of rxjs and older versions of systemjs. Let me know if this can be closed.
Note: for support questions, please use one of these channels: Chat: Gitter
I'm submitting a ... [x] bug report [ ] feature request [ ] question about the decisions made in the repository
Do you want to request a feature or report a bug? bug
What is the current behavior?
Getting an error in my production build:
I'm using the following seed: https://github.com/mgechev/angular-seed I can follow up with a repo demonstrating the error if necessary
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Angular version: 4.3
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
all