Add bootstrap and popper.js dependencie, yarn.lock update

[skoyah]

This PR fixes #52 .

[lucasmichot]

@skoyah - should you not also commit the updated version of yarn.lock then?

[skoyah]

@lucasmichot I'm kinda new when it comes to contributing, so I wasn't sure if the lock files should be committed to packages. Should I commit them?

[lucasmichot]

No worries @skoyah 👍 - Yes I would also commit the updated version of yarn.lock
You can this extra commit to this PR

[skoyah]

Ok @lucasmichot! Thanks for the info! Will do it asap!

[skoyah]

So @lucasmichot one more thing, how can I add the yarn.lock file to this PR? or should I delete this PR and create a new one?

It seems the yarn.lock file was not modified. But I do have a package-lock.json file untracked.

I've made some research and some people recommend to commit both files so people can use npm or yarn on their projects. But some other people say that when contributing to packages you should never commit those files.

So maybe @themsaid could help us on this subject.

[themsaid]

But we're not using Bootstrap anymore. We use TailwindCSS now.

[skoyah]

So @themsaid, that begs the question of maybe removing the unnecessary call to bootstrap an popper.js on the app.js file.