Remove npm/rules_js dependency for C++ only use cases (#7990)

When flatbuffers is being used from a project that has no use for
JavaScript, users encounter an error similar to the following:

    ERROR: Skipping '@com_github_google_flatbuffers//:flatbuffers': error loading package '@com_github_google_flatbuffers//': Unable to find package for @npm//:defs.bzl: The repository '@npm' could not be resolved: Repository '@npm' is not defined.
    WARNING: Target pattern parsing failed.
    ERROR: error loading package '@com_github_google_flatbuffers//': Unable to find package for @npm//:defs.bzl: The repository '@npm' could not be resolved: Repository '@npm' is not defined.
    INFO: Elapsed time: 0.023s
    INFO: 0 processes.
    FAILED: Build did NOT complete successfully (0 packages loaded)
        currently loading: @com_github_google_flatbuffers//

That's not ideal. Users that only care about C++ for example
shouldn't be forced to deal with rules_js and friends.

This patch attempts to fix that by moving the rules_js-specific things
into the `ts` and `tests/ts` directories. This should allow
non-JavaScript projects to ignore rules_js and friends completely.

Here I basically followed the `rules_foo` example from rules_js:

The idea is that flatbuffers has its own npm dependencies regardless
of what other projects may have. This means we should not force the
user to import flatbuffers's npm dependencies. The new
`ts/repositories.bzl` file is used by dependents to import
flatbuffers's dependencies. They can still import their own
dependencies. This cleanup allowed me to move all
JavaScript-specific stuff from the top-level directory into

There should be no changes in this patch in terms of functionality.
It's just a refactor of the rules_js call sites. Users will have to
add a call to the function in `ts/repositories.bzl` in their own
`WORKSPACE` file. They can use
`tests/ts/bazel_repository_test/WORKSPACE` as an example.

Co-authored-by: Derek Bailey <>
23 files changed
tree: 97dd663545295565a2f2ba8146b25d3afcfb739f
  1. .bazelci/
  2. .github/
  3. android/
  4. bazel/
  5. benchmarks/
  6. CMake/
  7. conan/
  8. dart/
  9. docs/
  10. examples/
  11. go/
  12. goldens/
  13. grpc/
  14. include/
  15. java/
  16. js/
  17. kotlin/
  18. lobster/
  19. lua/
  20. mjs/
  21. net/
  22. nim/
  23. php/
  24. python/
  25. reflection/
  26. rust/
  27. samples/
  28. scripts/
  29. snap/
  30. src/
  31. swift/
  32. tests/
  33. ts/
  34. .bazelignore
  35. .bazelrc
  36. .clang-format
  37. .clang-tidy
  38. .editorconfig
  39. .eslintrc.js
  40. .gitattributes
  41. .gitignore
  42. .npmrc
  43. BUILD.bazel
  44. build_defs.bzl
  46. CMakeLists.txt
  47. composer.json
  50. FlatBuffers.podspec
  53. package.json
  54. Package.swift
  55. Package@swift-5.5.swift
  56. pnpm-lock.yaml
  59. swift.swiftformat
  60. tsconfig.json
  61. tsconfig.mjs.json
  62. typescript.bzl

logo FlatBuffers

Build status BuildKite status Fuzzing Status OpenSSF Scorecard Join the chat at Discord Chat Twitter Follow Twitter Follow

FlatBuffers is a cross platform serialization library architected for maximum memory efficiency. It allows you to directly access serialized data without parsing/unpacking it first, while still having great forwards/backwards compatibility.

Quick Start

  1. Build the compiler for flatbuffers (flatc)

    Use cmake to create the build files for your platform and then perform the compliation (Linux example).

    cmake -G "Unix Makefiles"
    make -j
  2. Define your flatbuffer schema (.fbs)

    Write the schema to define the data you want to serialize. See monster.fbs for an example.

  3. Generate code for your language(s)

    Use the flatc compiler to take your schema and generate language-specific code:

    ./flatc --cpp --rust monster.fbs

    Which generates monster_generated.h and files.

  4. Serialize data

    Use the generated code, as well as the FlatBufferBuilder to construct your serialized buffer. (C++ example)

  5. Transmit/store/save Buffer

    Use your serialized buffer however you want. Send it to someone, save it for later, etc...

  6. Read the data

    Use the generated accessors to read the data from the serialized buffer.

    It doesn't need to be the same language/schema version, FlatBuffers ensures the data is readable across languages and schema versions. See the Rust example reading the data written by C++.


Go to our landing page to browse our documentation.

Supported operating systems

  • Windows
  • macOS
  • Linux
  • Android
  • And any others with a recent C++ compiler (C++ 11 and newer)

Supported programming languages

Code generation and runtime libraries for many popular languages.

  1. C
  2. C++ -
  3. C# -
  4. Dart -
  5. Go -
  6. Java - Maven
  7. JavaScript - NPM
  8. Kotlin
  9. Lobster
  10. Lua
  11. PHP
  12. Python - PyPI
  13. Rust -
  14. Swift - swiftpackageindex
  15. TypeScript - NPM
  16. Nim


FlatBuffers does not follow traditional SemVer versioning (see rationale) but rather uses a format of the date of the release.


To contribute to this project, see CONTRIBUTING.



Please see our Security Policy for reporting vulnerabilities.


Flatbuffers is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.