anchor.diff:  }
   ```
   
  -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 {url-meteor}[Meteor] client 💪.
  +Now each time we will change the definition of the type `Flag` or the type `Port` inside our {url-elm}[Elm] application, we will be sure to know if we have some stuff to fix in the {url-meteor}[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
  +Because we don't want to build manually our {url-elm}[Elm] application each time we make a change, we will setup the live reload
   
   We will install some packages to help us
   ```shell
  
positive.code: 
  === Create a Meteor package
  
  This {url-meteor}[Meteor] package will contain our Elm application and we will use this package inside the {url-meteor}[Meteor] application.
  
  We use a Package because it allows us to isolate our Elm application from the rest of the {url-meteor}[Meteor] context.
  It is also really useful if we want to remove our Elm application or if one we don't want to use Meteor {url-meteor}[Meteor] anymore.
  
  Let's start by creating some folders:
  ```shell
  mkdir -p packages/elm-app/{app,dist}
  ```
  
  The *app* folder will contain the sources of our Elm application (Elm, TS and CSS files).
  The *dist* folder will contain the result of the build made by {url-parcel}[Parcel].
  
  Because we will build with {url-parcel}[Parcel] and not with {url-meteor}[Meteor], we will create a new file at the root of the *meteor-elm-app* called *.meteorignore*
  
negative.code: 9 directories, 11 files
  ```
  
  In a first time, we will create a simple {url-elm}[Elm] application.
  
  Create a *Main.elm* file inside the folder *packages/elm-app/app/src* with this content:
  
  