Skip to content

Blerr511/bazel-npm-import-issue

Repository files navigation

Bazel Fails to Fetch fast-deep-equal Due to HTTP 304 Not Modified Error

I'm encountering an issue where Bazel fails to fetch the fast-deep-equal@3.1.3 package when using the npm_translate_lock rule from Aspect's rules_js. The build process halts with an error indicating that a GET request returned a 304 Not Modified status code, which Bazel does not handle properly.

This issue seems specific to the fast-deep-equal package, as other packages are fetched without any problems.

To reproduce the issue try to run

bazel run //:start

About

Minimal reproducable code for npm import issue

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published