You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was noticing that we bundle the dump-db tool in the release files, however we are actually shipping TS version, which of course currently does not work "out-of-the-box" with node (with currently released Node versions you would need to use some extra experimental flags).
We should correct that for future releases
The text was updated successfully, but these errors were encountered:
do we even want to ship dump-db with the releases?
In Electron releases e.g. – no one will be able to use it anyways, even if it was shipped as JS file (if I am not fully mistaken).
@pano9000 , my opinion is we shouldn't ship it at all for now, I don't see any benefit for the end user, at least for now.
And yes, we could ship it as an external tool.
For now it would be good not to include it, but I wouldn't spend too much time on it since it's a small file.
It should disappear on its own once we build the monorepo, since it'll go in a separate entrypoint.
Describe Task
Hi,
I was noticing that we bundle the
dump-db
tool in the release files, however we are actually shipping TS version, which of course currently does not work "out-of-the-box" with node (with currently released Node versions you would need to use some extra experimental flags).We should correct that for future releases
The text was updated successfully, but these errors were encountered: