Singular export bloats sidequest dependencies

[robcresswell]

Exporting everything as a singular sidequest dependency has quite a big impact on dependencies. Have you considered not bundling everything together? The dashboard for example, seems quite optional?

[GiovaniGuizzo]

Yes, that's why we don't bundle the backend drivers by default.

Interesting idea. Maybe bundling Sidequest's Dashboard separately is not a bad solution.

[robcresswell]

@GiovaniGuizzo Yeah I noticed the drivers were separate. Personally I don't think you need to make it so "magic" though by passing in the string driver name, that confused me a little.

The dashboard I noticed because it includes things like express. It mostly just felt quite heavy to include it by default. Not a huge issue, was just surprised to my lockfile increase in size so much when I added sidequest.

Thanks again for your work and fast responses!

[frederikheld]

+1 for bundling the dashboard separately.

I'm surprised, that the usage with the dashboard is your default use case.

IMHO it's a far more common use case to have one service add jobs and one or many runners to execute them. I would expect the dashboard to be a third separate service.

An application that is low-level enough to bundle everything into a monolith probably doesn't even need a task runner.