This is a round up of the first talk I did called “No metas todo en la misma bolsa: generando bundles por dispositivo” (which could be translated to the title of this article).

This is the second post in a series where I explain how to encapsulate the specific device logic into a Razzle plugin:

• Building bundles per device
• Avoiding boilerplate: Developing a razzle plugin (this post)
• Generalizing: Developing a webpack plugin (wip)

tl;dr; the idea is to reduce the needed boilerplate in order to serve particular experiences for each device.

This post will be more code related, I’ll show…

Some months ago the company where I work introduced a new policy called bring your own device (BYOD). Although, many already had set up the company’s google mail on our phone for free, now we were encouraged to use our personal device to work, but in order to do so, we had to install a Google App Device Policy. We were told that the objective of this policy was to protect sensible company’s data and that this app will only enforce us to have a lock code and device encryption.

According to google’s help:

Depending on how your administrator manages…

tl;dr Developing a gatsby-plugin-react-helmet-canonical-urls because gatsby-plugin-canonical-urls and gatsby-plugin-react-helmet do not play well together when using the canonical link.

Recently Dan Abramov announced that he would stop writing in medium, so, trying to set up my own gatsby blog was a great week-end project. I really didn’t want something fancy, just a blog site with a clean look that didn’t take me so many time to set up.

My first step was opening gatsby tutorial. Although, I must admit that the people from gatsby did a great work writing the docs, it seems to be targeted to new comers, i just…

Tl;dr; In the post i’ll show how to pass custom command line arguments to test suits run by Jest framework.

Lately i’ve using Tescafe for doing some end to end test (for those who doesn’t know, it is a Node.js tool to automate end-to-end web testing) and i’ve really like the proposed way to deal with configuration.

Basically, Tescafe has this question in their faq: How do I work with configuration files and environment variables? in which they just tell you “use an argument parser library to parse custom commands”.

This is a round up of the first talk I did called “No metas todo en la misma bolsa: generando bundles por dispositivo” (which could be translated to the title of this article).

This is the first post in a series where I explain how to build a react progressive web application that targets specific devices constraints:

• Building bundles per device (this post)
• Avoiding boilerplate: Developing a razzle plugin
• Generalizing: Developing a webpack plugin (wip)

tl;dr; the idea is to incrementally start serving particular experiences for each device (i.e: Mobile / Desktop) in the lazy programming way.

In this post…