anchor.diff:  
   NOTE: Take care of the first line if you don't use SCSS but a `main.css` file
   
  -=== Build with parcel
  -But... wait... why do we use Parcel? Why don't we use the Elm make command? Why don't we use the Meteor bundler for css?
  -
  -It is a personal choice, imo using Parcel is easier to build my Elm app, mixing Elm, TS and SCSS. Also it is easier to use Tailwind, because most of the packages I found (PostCSS, PurgeCSS) where not maintened anymore.
  -
  -Because the dist content does not exist yet, we must build a first time manually with parcel
  -
  -update the `package.json` file to add the script
  -```js
  +=== Build with Parcel
  +
  +Let's create a build script in our `package.json` file:
  +```json
   "elm:build": "parcel build packages/elm-app/app/index.ts -d packages/elm-app/dist --out-file elm-app.js --no-cache",
   ```
   
  -and run
  -```
  +This script will build our application in a file `elm-app.js` (and `elm-app.css`) and put it in the folder `packages/elm-app/dist` (the one we added in our `.gitignore`) 
  +
  +
  +We can test our script
  +
  +```shell
  +#under meteor-elm-app
   meteor npm run elm:build
   ```
   
  -If everthing is ok, you should see
  +If everything is ok, you should see these lines:
   
   image::https://user-images.githubusercontent.com/2006548/84450020-4ea43680-ac4f-11ea-9b45-ce0dfb572835.png[]
   
  -=== Add our meteor package
  -in your shell, execute
  -```
  +
  +=== Add our package to Meteor 
  +
  +We have a package, but we must add it in our Meteor configuration.
  +
  +NOTE: you must have run the previous build command before adding the package because without a dist folder, you will not be able to add this package.
  +
  +Execute this command to add the package
  +
  +```shell
  +#under meteor-elm-app
   meteor add elm-app
   ```
   
  
positive.code: 
  image::https://user-images.githubusercontent.com/2006548/84450082-7abfb780-ac4f-11ea-92f4-db936ee6f726.png[]
  
  === Post install
  To avoid to have to compile manually each time someone clone the repository, we will add a `postinstall` script:
  
  ```json
  "postinstall": "npm run elm:build",
  ```
  
  == Use the Elm in our Meteor client
  Now that we have our Elm application, it is time to import it in the client part of our Meteor application
  
  update your `client/main.ts`
  
  ```ts
  import { init } from "meteor/elm-app";
  
negative.code: }
  ```
  
  Now each time we will change the definition of the type `Flag` or the type `Port` inside our Elm application, we will be sure to know if we have some stuff to fix in the Meteor client 💪
  
  == Live Reload
  Because we don't want to build manually our Elm application each time we make a change, we will setup the live reload
  