player-ui / rules_player Goto Github PK

Since Github doesn't guarantee the integrity of the auto created archives of tags that are created during a release, it is possible for the checksum of the rules to change after release. To get around this we should create that archive ourselves. There is still the possibility that transitive dependencies will have their checksum change but this is really all we can do.

When dependencies are declared in a rule, when they get resolved into a package json, they get resolved into the flattened first package in tree

This is prevalent in the @player-ui/player package where the first dependency added is for binding-grammar instead of binding

rules_nodejs isn't maintained anymore. We should migrate to rules_js

Add a usage example like so:

http_archive(
    name = "rules_player",
    strip_prefix = "rules_player-0.5.0",
    urls = ["https://github.com/player-ui/rules_player/archive/refs/tags/v0.5.0.tar.gz"],
    sha256 = "76291ffd332cee690db7b91ae37b7b2388104b09230f7063bfd104a48a926f8b"
)

Will require us to compute the correct sha256 hash during build

For our jest tests in the js pipeline, we should create a run target for updating the snapshots

There are examples in the main rules_nodejs repo for doing this: https://github.com/bazelbuild/rules_nodejs/blob/6ee1e529390cadba1add23722a0011a990c9d461/examples/jest/jest.bzl#L39-L49