Move the frontend into its own package

[rgaiacs]

In #1856, @yuvipanda wrote

Use react-router for URL parsing. This makes the BinderHub UI a SPA, which may be split into its own package separately in the future if so desired.

@rgaiacs and @arnim were talking and jupyterhub/mybinder.org-deploy#3264 will benefit of move the frontend into its own package to allow "embed" the frontend in a third-party website.

sequenceDiagram
    actor User
    participant browser
    participant gesis as lorem.ipsum.com
    participant binderhub as gesis.mybinder.org
    participant jupyterhub as hub.gesis.mybinder.org
    User->>browser: Type URL
    browser->>gesis: Make request
    gesis->>browser: Send response
    browser->>browser: Render form
    User->>browser: Fill form
    browser->>binderhub: Make build request
    binderhub->>binderhub: Build container
    binderhub->>browser: Inform of successful build
    browser->>jupyterhub: Make launch request
    jupyterhub->>jupyterhub: Start container
    jupyterhub->>browser: Inform of running container
    browser->>browser: Redirect to Jupyter Lab interface
    User->>browser: Python code
    browser->>jupyterhub: Run Python code

Loading

[rgaiacs]

Hello,

I'm returning to this enhancement proposal. When I was working on #1956, I did struggle with webpack and I could not implement what I wanted. I decided to start small and I think that I got something in the direction that I want: https://github.com/rgaiacs/mwe-esbuild Because I'm probably making novice mistakes when thinking about this, I appreciate feedback before start a new pull request.

@yuvipanda do you have strong reasons against use esbuild to bundle the new NPM package?