PrimeNg+Webpack+IIS

UI Components for Angular
Post Reply
microdeveloper
Posts: 82
Joined: 21 Mar 2016, 19:42

09 May 2016, 16:32

Hi i am facing sesiorus issues in deployment of my app. I followed the PrimeNG+Webpack sample app https://github.com/primefaces/primeng-q ... rt-webpack and create bundle and run and successfully run the app on local machine.
But when i host the same PrimeNG sample webpack app on IIS Windows Server app does not work and i am facing following problems in browser console.

404 (Not Found)scheduleTask @ bundle.js:213ZoneDelegate.scheduleTask @ bundle.js:448Zone.longStackTraceZoneSpec.onScheduleTask @ bundle.js:1545ZoneDelegate.scheduleTask @ bundle.js:445Zone.scheduleMacroTask @ bundle.js:385(anonymous function) @ bundle.js:234send @ VM60:3XHRImpl.get @ bundle.js:26066DirectiveNormalizer.normalizeTemplate @ bundle.js:38154DirectiveNormalizer.normalizeDirective @ bundle.js:38127(anonymous function) @ bundle.js:35169RuntimeCompiler._loadAndCompileComponent @ bundle.js:35169RuntimeCompiler.resolveComponent @ bundle.js:35150(anonymous function) @ bundle.js:16389(anonymous function) @ bundle.js:16580ZoneDelegate.invoke @ bundle.js:435NgZoneImpl.inner.inner.fork.onInvoke @ bundle.js:16991ZoneDelegate.invoke @ bundle.js:434Zone.run @ bundle.js:328NgZoneImpl.runInner @ bundle.js:17022NgZone.run @ bundle.js:16919ApplicationRef_.run @ bundle.js:16578coreLoadAndBootstrap @ bundle.js:16386bootstrap @ bundle.js:6606(anonymous function) @ bundle.js:53__webpack_require__ @ bundle.js:20(anonymous function) @ bundle.js:40(anonymous function) @ bundle.js:43
bundle.js:25635EXCEPTION: Failed to load app/app.component.html
bundle.js:25626EXCEPTION: Failed to load app/app.component.htmlBrowserDomAdapter.logError @ bundle.js:25626BrowserDomAdapter.logGroup @ bundle.js:25636ExceptionHandler.call @ bundle.js:8135(anonymous function) @ bundle.js:16584ZoneDelegate.invoke @ bundle.js:435NgZoneImpl.inner.inner.fork.onInvoke @ bundle.js:16991ZoneDelegate.invoke @ bundle.js:434Zone.run @ bundle.js:328(anonymous function) @ bundle.js:683ZoneDelegate.invokeTask @ bundle.js:468NgZoneImpl.inner.inner.fork.onInvokeTask @ bundle.js:16982ZoneDelegate.invokeTask @ bundle.js:467Zone.runTask @ bundle.js:368drainMicroTaskQueue @ bundle.js:586ZoneTask.invoke @ bundle.js:538
bundle.js:25635EXCEPTION: Error: Uncaught (in promise): Failed to load app/app.component.html
bundle.js:25626EXCEPTION: Error: Uncaught (in promise): Failed to load app/app.component.htmlBrowserDomAdapter.logError @ bundle.js:25626BrowserDomAdapter.logGroup @ bundle.js:25636ExceptionHandler.call @ bundle.js:8135(anonymous function) @ bundle.js:16553schedulerFn @ bundle.js:15005SafeSubscriber.__tryOrUnsub @ bundle.js:15754SafeSubscriber.next @ bundle.js:15703Subscriber._next @ bundle.js:15653Subscriber.next @ bundle.js:15617Subject._finalNext @ bundle.js:15219Subject._next @ bundle.js:15211Subject.next @ bundle.js:15168EventEmitter.emit @ bundle.js:14994NgZone._zoneImpl.ng_zone_impl_1.NgZoneImpl.onError @ bundle.js:16816NgZoneImpl.inner.inner.fork.onHandleError @ bundle.js:17012ZoneDelegate.handleError @ bundle.js:439Zone.runGuarded @ bundle.js:345_loop_1 @ bundle.js:599drainMicroTaskQueue @ bundle.js:606ZoneTask.invoke @ bundle.js:538
bundle.js:25626STACKTRACE:BrowserDomAdapter.logError @ bundle.js:25626ExceptionHandler.call @ bundle.js:8137(anonymous function) @ bundle.js:16553schedulerFn @ bundle.js:15005SafeSubscriber.__tryOrUnsub @ bundle.js:15754SafeSubscriber.next @ bundle.js:15703Subscriber._next @ bundle.js:15653Subscriber.next @ bundle.js:15617Subject._finalNext @ bundle.js:15219Subject._next @ bundle.js:15211Subject.next @ bundle.js:15168EventEmitter.emit @ bundle.js:14994NgZone._zoneImpl.ng_zone_impl_1.NgZoneImpl.onError @ bundle.js:16816NgZoneImpl.inner.inner.fork.onHandleError @ bundle.js:17012ZoneDelegate.handleError @ bundle.js:439Zone.runGuarded @ bundle.js:345_loop_1 @ bundle.js:599drainMicroTaskQueue @ bundle.js:606ZoneTask.invoke @ bundle.js:538
bundle.js:25626Error: Uncaught (in promise): Failed to load app/app.component.html
at resolvePromise (bundle.js:650)
at PromiseCompleter.reject (bundle.js:627)
at bundle.js:16583
at ZoneDelegate.invoke (bundle.js:435)
at Object.NgZoneImpl.inner.inner.fork.onInvoke (bundle.js:16991)
at ZoneDelegate.invoke (bundle.js:434)
at Zone.run (bundle.js:328)
at bundle.js:683
at ZoneDelegate.invokeTask (bundle.js:468)

User avatar
DarthMaul
Posts: 583
Joined: 23 Nov 2015, 21:20

09 May 2016, 22:25

I think webpack needs some configuration for runing with IIS but i can't find any i'll look into that and get back to you.

microdeveloper
Posts: 82
Joined: 21 Mar 2016, 19:42

10 May 2016, 09:53

Yes please because our apps are ready for beta release and my whole team facing deployment issues, Please help us and finally i also tried the same webpack settings provided by PrimeNG and it didn't word either.

rmarchiori
Posts: 10
Joined: 25 Apr 2016, 16:34

27 May 2016, 16:58

If you're using virtual directory try to set the base element with it in your index.html. It might be the reason you're getting the 404.

Code: Select all

<base href="/VirtualDirectory/">

Post Reply

Return to “PrimeNG”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 6 guests