Why deprecate docStore in favour of byteStore in ParentDocumentRetriever?

[jambudipa]

What is the thinking behind this deprecation?

I don't want to store my documents in byte format.

I would like to be able to read them and their metadata in the docstore I am creating for MongoDB. I see from the source that, at the moment, when a byteStore is passed in to MultiVectorRetriever, a plain old store is created to proxy the byte store!

So the is the purpose of this?

[habasefa]

byeteStore is not working for me(Javascript version), do I need to migrate to TypeScript?

const byteStore = new InMemoryStore<Uint8Array>();
This produces an error in js.

I am getting this error when I removed the type and run my code for MultiVectorRetriever

node:internal/errors:490
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/stores/doc/in_memory' is not defined by "exports" in C:\Users\nazri\OneDrive\Desktop\Javascript Excercise\langchain\node_modules\@langchain\community\package.json imported from C:\Users\nazri\OneDrive\Desktop\Javascript Excercise\langchain\index.js
    at new NodeError (node:internal/errors:399:5)
    at exportsNotFound (node:internal/modules/esm/resolve:361:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:697:9)
    at packageResolve (node:internal/modules/esm/resolve:872:14)
    at moduleResolve (node:internal/modules/esm/resolve:938:20)
    at defaultResolve (node:internal/modules/esm/resolve:1153:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

[habasefa]

I solved this problem when I imported byestore from:

import { InMemoryStore } from "langchain/storage/in_memory";