git clone https://github.com/amrdraz/workshop-important-tools
Amr Draz
we introduce a problem
we think about solutions if no one knows it
we talk about solutions
we practice/understand the latest solution through exercise
prompt questions
summarize what we learn (trying to remember makes it easier to remember later)
This is meant for you to remember and stay engaged (see book Make it stick)
Sometimes developers have to do work that is not fixing bugs or developing new features
deploy application
compress code
check you didn’t break anything
Developer time is expensive so we want to make their job easier
DX and DevOps developers are concerned with that
Dev Ops is Development Operations (as opposed to Application Feature)
DX is Developer Experience (like User Experience) we create tools that reduce the cognitive load a developer has to deal with.
git clone https://github.com/amrdraz/workshop-important-tools
JS developers only see sytax errors in the browser (at runtime)
We want to detect syntax errors early on
We want to enforce best practice
write a parser that detect "rule" violations and notifies the programer
Clone the repo if you didn't already
Copy the content of `code/02-eslint/being` to your root
Install the vsCode eslint package
Try to follow the instruction on eslint getting started
Fix the errors in index.js in src
What is babel good for?
We want developers to be able to split their application into modules so that it’s easier to manage, but...
We want to deliver our applications as fast as possible to users
We want them to load the smallest amount of files and have browsers parse the least amount of code
Webpack solves all these problems and more, but to understand what it's doing we will take a step back over the next 2 workshop, as we observe the development of ESModules.
cp -R ./code/05-webpack-IIFE/begin/* .
npm run serve