Finally, after a long awaited time, the book is here. I just completed writing a book, Full Stack Web Development with Vue.js and Node which talks about how we can build web applications using the technologies in MEVN stack i.e. (MongoDB, Express.js, Vue.js and Node.js). More details on the book can be found here(https://www.packtpub.com/web-development/full-stack-web-development-vuejs-and-node) in Packt Publishing.

If you are a web developer and want to try hands on building web applications learning just one programming language i.e. JavaScript, then this book is for you.

The book guides you through the technology stack called MEVN which just replaces the frontend layer of Angular.js from MEAN or React.js from MERN and introduces Vue.js.

This book guides you through building a web application with Express.js which is a Node.js framework followed by adding the database layer with MongoDB and then the frontend layer with Vue.js to create a robust application.

Who the book is for?

This book is suitable for people who have the basic understanding of the following things:

• Knowledge of HTML, CSS and JavaScript
• Knowledge of MVC architecture
• Knowledge of MEAN and MERN stacks is the cherry to the cake

Key takeaways from this book:

• Learn to install Node.js and other software packages required to build a full application
• Build an application using Express.js
• Create Schemas using Mongoose
• Build RESTful APIs using Express.js
• Build a Single Page Application using Vue.js and Express.js
• Learn to leverage Vuex to build complex applications
• Add test cases to improve the reliability of the application
• Add authorization using passport.js and learn about several Oauth Strategies that passport.js provides
• Learn how to deploy apps on Heroku using Github

Sneak peek of the application

Throughout the book, we will be building a movie rating application with the following features:

• A home page that lists all the movies

• Ability to add movies

• Ability for users to sign up and sign in — using both local authentication along with several OAuth Strategies

• The user will be able to rate a movie

Start Reading the Book

You can grab yourself a copy from Amazon from the following link: Full-Stack Web Development with Vue.js and Node

Also, there is a launch discount as well for the ebook version which you can get from Packt Publishing here: https://www.packtpub.com/web-development/full-stack-web-development-vuejs-and-node

✉️ Subscribe to CodeBurst’s once-weekly Email Blast, 🐦 Follow CodeBurst on Twitter, view 🗺️ The 2018 Web Developer Roadmap, and 🕸️ Learn Full Stack Web Development.

Inside the book — Full-Stack Web Development with Vue.js and Node was originally published in codeburst on Medium, where people are continuing the conversation by highlighting and responding to this story.

If you are using Rubocop as a code analyzer and following its guidelines as a standard for your project, then like me you also might have faced the annoyance of running Rubocop on each and every modified file individually. Its boring and a little time consuming as well. Hence, its lot more productive to run it only on the updated files and for once.

There are two ways to run Rubocop on modified files:

[1] Before committing
To view the list of files that have been modified, you can do:

git ls-files -m

This lists all the modified files regardless of the extensions as well as the deleted files. To exclude deleted files you can do:

git ls-files -m | xargs ls -1 2>/dev/null

Again, if you wish to view only the modified files with .rb extension, you can do:

git ls-files -m | xargs ls -1 2>/dev/null | grep '\.rb$'

Hence, the final command to run Rubocop for modified files is:

git ls-files -m | xargs ls -1 2>/dev/null | grep '\.rb$' | xargs rubocop

[2] After committing
There are two ways to view the list of changed files after you have committed. First is to compare the changes with master or you can compare it with the current upstream.

To compare with master:

git diff-tree -r --no-commit-id --name-only head origin/master

To compare with current upstream:

git diff-tree -r --no-commit-id --name-only @\{u\} head

Note: This won’t work if you haven’t yet set up a remote branch.

Hence, the file command to run Rubocop for modified files is:

git diff-tree -r --no-commit-id --name-only head origin/master | xargs rubocop

or

git diff-tree -r --no-commit-id --name-only @\{u\} head | xargs rubocop

With this, you will be saving quite a time. To top if off, you can also create aliases for these.

Running Rubocop Only On Modified Files was originally published in Devnetwork on Medium, where people are continuing the conversation by highlighting and responding to this story.