Closed hanneskaeufler closed 1 year ago
Modules such as https://registry.bazel.build/modules/apple_rules_lint don't have the compatibility_level set in their MODULE.bazel files. This is fine, since that is an optional attr with a default, see https://bazel.build/rules/lib/globals#module
compatibility_level
However, querying for that attr returns (missing), which is parsed to NaN and leads to the dreaded "hydration error" in next js during development, and of course to nothing being rendered in the final output in prod.
(missing)
NaN
Falling back to the default of 0 fixes that.
0
Modules such as https://registry.bazel.build/modules/apple_rules_lint don't have the
compatibility_levelset in their MODULE.bazel files. This is fine, since that is an optional attr with a default, see https://bazel.build/rules/lib/globals#moduleHowever, querying for that attr returns
(missing), which is parsed toNaNand leads to the dreaded "hydration error" in next js during development, and of course to nothing being rendered in the final output in prod.Falling back to the default of
0fixes that.