React is really easily explained as a JS library for creating User Interfaces, so React is always just part of your technology stack. React is really good at building single page apps but unlike Angular you need to add libraries to React such as React Router to handle routing. JSX React is written in JSX so due to not all browsers supporting it we need to include babel which is used to compile the JSX…
If you have not heard of or used webpack stats data command before then it is time to take a look into it. The command generates a JSON file which contains detailed information and statistics about the modules used within the application. Stats Data command is an invaluable tool to try to understand and analyse an applications dependencies graph which is the most handy tool we can have when doing any deep level application debugging.…
I thought I would put together some small notes around debugging Javascript in the Browser. Linters Yes Linters have nothing to do with the browser, however to discuss JavaScript Debugging in 2019 it is impossible not to start with Linters. Why Linters? Well for starters when I started coding for the web there was nothing like linters that existed. This meant that alot of your errors where simple ones that could have been picked up…
There has been increasing talk in the CMS communities around lando as a tool to use with Docker for the ease of local development. I have used it on a few projects now and I really enjoyed the speed and reliability, if you are a fan of Docker Compose this is not for you but if you are a fan of reduced onboard time then lando could be your friend. How does it help? Basically lando…
Recent big news in WordPress has been around the new release of the new Block Editor for Gutenberg. In Gutenberg we now lay our pages out by adding blocks for the type of content /layout/feature we want displayed on the page. Gutenberg comes with a stack of default blocks for adding text, media, layout etc however there are many times when we will want to create out own blocktypes. Key thing to note is that…
There really is only two small commands that you need to run to get VMware player working on Fedora; You will need to install gcc in order to get VMWare tools working; 32bit 64bit VMware-Player-6.0.1-1379776.i386.bundle needs to be replaced with the name of the version that you are trying to install.