[AngularJS] Re: Angular2 + Express.js running on the same port?

http://stackoverflow.com/questions/37559853/angular-2-rc-with-express-server-instead-of-lite-server/ I've just asked in stackoverflow and got some solution from it On Thursday, May 12, 2016 at 10:00:31 PM UTC+5:30, Kyle Thomas wrote: > > Is it possible to start up node and have both run on the

Re: [AngularJS] Re: Angular2 + Express.js running on the same port?

I was able to get it running using the latest packages with Gulp. Thanks for the assistance in answering all my noob questions. Cheers Zlatko! On Mon, May 16, 2016 at 1:51 PM, Zlatko Đurić wrote: > Ok, that is a good progress. You now have a broken app that you can serve.

Re: [AngularJS] Re: Angular2 + Express.js running on the same port?

Ok, that is a good progress. You now have a broken app that you can serve. All you need to do is fix the build process. Now, the error bellow suggests many things, but I would bet on version changes. There were a lot of breaking changes during Angular2 beta issues - almost each new beta

Re: [AngularJS] Re: Angular2 + Express.js running on the same port?

This application started as a yoeman - generator-angular-fullstack and uses grunt, but since I'm converting it over to NG2 i'm running a hybrid with the upgradeAdpater so I can run both. The yeoman generator was running everything through the .tmp. I guess I'll look into seeing if I can modify

Re: [AngularJS] Re: Angular2 + Express.js running on the same port?

I can run express by itself by issuing: npm run server which does: "server": "cd server && node index.js" This opens express on port 3001 When I run the application (client) which is stored in /client I use: npm run go which does: "go": "concurrent \"npm run tsc:w\" \"npm run serve\" " This

Re: [AngularJS] Re: Angular2 + Express.js running on the same port?

Oh, well, that's because you didn't build your Angular app for deployment. Try running "npm build" if you're using one of the more popular packs. Then you'll get a "dist/production" directory or something similar - _that_ is the folder you need to serve. (Or at the very least, look in your

[AngularJS] Re: Angular2 + Express.js running on the same port?

When I do that I get: > cd server && node index.js info: Express server listening on 3001, in development mode GET /node_modules/systemjs/dist/system.js 304 11.320 ms - - GET /node_modules/es6-shim/es6-shim.js 304 8.689 ms - - GET /node_modules/angular2/bundles/angular2-polyfills.js 304 10.217

[AngularJS] Re: Angular2 + Express.js running on the same port?

On Thursday, May 12, 2016 at 6:30:31 PM UTC+2, Kyle Thomas wrote: > > Is it possible to start up node and have both run on the same port? > Node app as a backend API and the angular app as a frontend? Yeah, relatively simple, if you let Node serve your angular stuff. Look up express.static()