Use Webpack

[gary-kim]

Closes #252

Being a bit conservative with the milestone for now. 😄

There's quite a lot more that could be done for cleanup but I think it'd be better to put that in a follow-up PR.

EDIT: Someone who has access to settings for the repo: could you enable the projects feature? I'd like to make a project for migration to Vue.
EDIT 3: Once this is done, PR incoming for migrating admin settings to Vue.
EDIT 4:
@eneiluj @jancborchardt package-lock.json and composer.lock being in the .gitignore file caused me some confusion. I just read #44.
I just removed those lines from .gitignore and committed those files in this PR.
Just for future reference, package-lock.json and composer.lock should be committed into source control: package-lock.json documentation && composer.lock documentation 😄. (I don't mean that with any negative intent)

[ChristophWurst]

Just for future reference, package-lock.json and composer.lock should be committed into source control: package-lock.json documentation && composer.lock documentation smile. (I don't mean that with any negative intent)

Yes!

[ChristophWurst]

+7,999

Are you trying to sell the PR? :P

[ChristophWurst]

Seems good in general.

Neither did I test this nor have I a clue about the code of the app 🙊

[tacruc]

How does this work together with #217?
As I see both PRs add some webpack.prod.js for example.
@paulschwoerer Cloud you review, too.

[gary-kim]

Huh, interesting. This is going to be a messy merge. #217 set up a lot of the same things as this PR with the main difference being that #217, the setup was just for the new feature and here, the idea is to simply migrate all of the JS for the app.

Considering the name of #217, I didn't think to look in it for a change like this.

[tacruc]

Thats what I was afraid of. What would be the besteht order of merging them?
@paulschwoerer

[paulschwoerer]

Please have a look at the @nextcloud/router dependency in package.json. Shouldn't it be a production dependency?

Apart from that LGTM

[paulschwoerer]

@gary-kim Solid work!

What would be the besteht order of merging them?

It should actually be quite straightforward to merge this with the changes I did. I'd suggest to merge this commit first and I'll take care about merging the changes into #217 before merging #217 into master.

I'd like to make a project for migration to Vue.

I was also interested in migrating the app to Vue, I'd be glad to lend a hand in doing so. In my PR you might find some useful components, that can be expanded on.

[gary-kim]

@gary-kim Solid work!

You too @paulschwoerer!

In my PR you might find some useful components, that can be expanded on.

Thank you! I'll be sure to make good use of those.

[tacruc]

Is it ready to merge?

[gary-kim]

Is it ready to merge?

🚀 Ready to merge!

EDIT: Actually, let me add the node_modules to the ignore for release first 🙈
EDIT 2: Done!