Configuring Webpack is quite easy but it may become more difficult if there are many environments and requirements. I’ve included Webpack in different projects recently and I would like to share with you an easy way to configure it. I’m sure there are many different ways to configure Webpack, maybe better, but I’m just going to compare two of them:
In one project I’m working on, we have migrated from a non-standard building tool to Webpack. This change has allow us to use a standard module system to import/export our code instead of the legacy builder we were using to just concatenate code.
Javascript modules are needed to maintain the principles of encapsulation and dependency.
As a project grows, it is useful to reuse pieces of software developed in isolation. When one of these pieces of software is brought into a project, a dependency between them is created. For example, many projects nowadays relay in some JS framework like Angular, ReactJS, VueJS or others. This concept is known as dependency.
When a dependency is created between these pieces of software it is of importance that no conflicts arise. This is known as encapsulation. Encapsulation is important because it isolates and guarantees that there won’t be any interference between different pieces of code.
I’ve been working these days using Angular2 for the first time and this is what I have to say.
Before starting with this text, I have to say this opinion is totally personal and based in my own experience. Talking about my experience: I’ve been working with Angular 1 for more than three years. I started with Angular 1.2.3 and I’m currently using version 1.5.8 with these rules:
Many modern projects separate the backend from the frontend user interface. The bakend usually handles incoming requests and responses with some information in JSON or XML.
When you are working with an architecture like this, your API needs to be exposed in a secure way and here is where Auth0 will simplify your design.
In this post I’m going to explain how I have integrated a website made with AngularJS with an API using ExpressJS and secured with Auth0.
Summer has arrived. I can’t forget those summer nights at my village when I was young, looking at a bright night sky with a lot of glittering stars.
The infinite of the sky made me small, leaving my mind at a point I thought about anything and everything at the same time, braindead, stunned, relaxed.
I looked at a whole sky without paying attention to any specific star, seeing satellites crossing the sky in a “perfect” straight line. I loved those nights as much as I loved the universe although I don’t know as much I’d like about it.
If you have read my previous article about chaining promises, you’ll know I love using small functions in “then” methods, but sometimes chaining is not that simple.
For example, when you have to execute in your “then” method a function receiving two parameters it is not possible… or it is?
In these cases you can use some alternatives as seen below:
In the project I’m working on there is a limit of 80 chars per line, in fact, in other personal projects I have, I also set a limit of 80 chars per line.
80 chars limit is one of the most used limit when programming, but why are we using this limit and no other?