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'm happy to see the 0.0.5 release (not tagged?) with many other storages.
However, most of them need extra packages (monk, ...) that are not is the botkit package.json file.
So when installing, it does not work.
And if you had them all in the botkit package.json, it will install lots of useless packages.
What about keeping only the "jfs" as default (light) and move the others in other npm packages like botkit-storage-mongo, botkit-storage-redis and so on?
The text was updated successfully, but these errors were encountered:
@tilap and @robguilfoyle, I've been discussing this with @benbrown and it seems like a good move. Major kudos to either of you if create the botkit-storage-* npm packages!
Hi,
I'm happy to see the 0.0.5 release (not tagged?) with many other storages.
However, most of them need extra packages (monk, ...) that are not is the botkit package.json file.
So when installing, it does not work.
And if you had them all in the botkit package.json, it will install lots of useless packages.
What about keeping only the "jfs" as default (light) and move the others in other npm packages like botkit-storage-mongo, botkit-storage-redis and so on?
The text was updated successfully, but these errors were encountered: