Adding AngularJS to an existing node.js/express application, NOT!

Stevo Perisic
Jul 22, 2017 · 2 min read

I am currently working on an node/express application and have arrived at a point where I am not satisfied with all of the DOM being rendered on the server. At this point I am strongly considering moving the DOM to the front-end code. After some consideration as to should I go vanilla JS or React or Angular I decided to try my hand out in the new Angular JS.

Update:

This app is for my startup, and the golden rule of delivering startup apps is to get something out as fast as possible, the client is waiting and the application itself can benefit from being used by actual users other than just myself. So I think I need to swallow my ego and hold off on any refactoring at the moment. Concentrate on delivering the basic functionality as fast as possible in the fastest way.

Forget about petty code and MVC and separation of the presentation layer. All that is bullshit if it adds another two months to the delivery timeline of an already late application. Get on with it the way you started and DELIVER!

End Update

Here are the steps, good and bad experiences I have encountered while refactoring my application form node/express to node/express/angular code stack. -> What a bunch of crap!

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade