Skip to content

[JS] npm packages depends on outdated flatbuffers-esm #2640

@tarekrached

Description

@tarekrached

Not sure what the root cause is here, or if this is even a real issue, but I figured I'd flag it...

It looks like the apache-arrow npm package (and the @apache-arrow/* packages) are pointing at an out of date fork of flatbuffers from @trxcllnt, which can be seen with:

npm view apache-arrow@0.3.1 dependencies.flatbuffers

which shows github:trxcllnt/flatbuffers-esm instead of 1.9.0, which is what js/package.json leads me to believe it should be.

The description of the trxcllnt/flatbuffers-esm repo says:

temporary repo to use in Arrow until google/flatbuffers#4504 is merged

That PR was merged on Dec 1, 2017, so I think we're good to point back at mainline flatbuffers.

Since the package.json in this repo doesn't match that on npm, I'm guessing this is a packaging / deployment issue. Let me know if there's anything I can do to help resolve this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions