-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is arrow a peer dependency? #31
Comments
We found that when different parts of an application depended on By making |
What if instead you make it a dependency but you allow any version (*)? Would the bundler resolve the dependency to a single version rather than a copy? I guess the underlying issue is that arrow does not follow semantic versioning. |
We do depend on some fixes & features in the newer versions, so "*" isn't really correct. I'm not sure whether it would resolve the multi-copy issue. It's hard to reason about the many different dependency and bundler configurations that applications might use. The updated SDK I'm working on changes the dependency structure. (In particular, we'll depend on duckdb-wasm using NPM, instead of using a version built & hosted by MotherDuck.) As I work on that, I'll investigate whether there's a simpler solution to this problem that doesn't require peer dependencies. |
Shouldn't it be a normal dependency with a flexible range of allowed versions? Having two package versions seems fishy.
The text was updated successfully, but these errors were encountered: