MEAN Stack

As I'm spending my weekend familiarizing myself with the MEAN (Mongo, Express, AngularJS, Node) stack, I'm reminded and amused how quickly the web moves. Just as I'm getting some packages/dependencies set up using npm, I see a blog that highly suggests to start using yarn for new projects.

Considering I'm following along with some legacy guides, I'll stick with npm, but I'll have to scratch that use-the-newest-tech itch and take a look at yarn later.

Edit: What's better than having 5+ instances of command prompt (to run nodemon, mongo, etc.)? 1! So I downloaded Cmder and all is clean again.

Edit 2: Hours later and with some debugging resulted in the image below. At the moment it's bare-bones -- Bootstrap for the interface, Express for the server, AngularJS for some basic data binding of course data, and Jade for HTML generation. I haven't worked much with Bootstrap, but I love how easy it is to create a clean, visually appealing layout.

The web app is version controlled via GIT and uploaded to Heroku. I've been following a guide from 2016, so needless to say, had to work around some compatibility issues between dependencies and ignore the "this API call is deprecated! use this instead" messages since this is just a quick test application.

In the past I've mainly interacted with GIT using the context-menu based TortoiseGIT for personal projects instead of command line, so that was a bit different -- command line actually seems to be the norm for open source web development. And this is much different than the workflow I've gotten used to at work with .NET development (Visual Studio and NuGET), which is all interface-based.

With the basic structure and dependencies up now, I can move on to more interesting topics: security, testing, and the usual CRUD for data.

PrintView Printer Friendly Version

EmailEmail Article to Friend

References (3)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
« Hello, Android | Main | Lunch & Learn - Progressive Web Applications »