[Bug]: why `https://registry.bazel.build/modules/boost` was `404`

[kekxv]

What happened?

https://registry.bazel.build/modules/boost

https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/boost

Version

Development (host) and target OS/architectures:

Output of bazel --version:

Version of relevant rules from the WORKSPACE or MODULE.bazel file:

Language(s) and/or frameworks involved:

How to reproduce

Any other information?

No response

[hofbi]

https://github.com/bazel-contrib/bcr-ui/actions/runs/19128827030 is broken since #6179 landed. @UebelAndre FYI.

[UebelAndre]

https://github.com/bazel-contrib/bcr-ui/actions/runs/19128827030 is broken since #6179 landed. @UebelAndre FYI.

I don't know what that is. Why does the error reference 1.83.0?

Error occurred prerendering page "/modules/boost.json/1.83.0". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: EEXIST: file already exists, mkdir '/home/runner/work/bcr-ui/bcr-ui/.next/export/modules/boost.json'] {
  errno: -17,
  code: 'EEXIST',
  syscall: 'mkdir',
  path: '/home/runner/work/bcr-ui/bcr-ui/.next/export/modules/boost.json'
}
Export encountered an error on /modules/[module]/[version]: /modules/boost.json/1.83.0, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null
 ELIFECYCLE  Command failed with exit code 1.

[Wyverald]

It's because #6179 added a module called "boost", and next.js generates a file "modules/boost.json" in its export directory when building a static website. But that conflicts with the existing module "boost.json". (Essentially, having two module named "X" and "X.json" for any X would have caused the same problem.)

See bazel-contrib/bcr-ui#230 for @alexeagle's attempt to fix this -- doesn't seem to be successful, unfortunately. If anyone familiar with next.js can jump in with a fix, that'd be great.

[hofbi]

Should be solved now. PR landed and UI is updating again.