Open gregmagolan opened 3 days ago
@rahul-roy-glean listed a number of them in this comment https://github.com/aspect-build/rules_js/issues/1637#issuecomment-2314514337:
custom_postinstalls = {
"pngjs": "chmod -R a+X *",
"websocket-extensions": "chmod -R a+X *",
"pretty-format": "chmod -R a+X *",
"readdirp": "chmod -R a+X *",
"serve-static": "chmod -R a+X *",
"serialize-javascript": "chmod -R a+X *",
"supports-preserve-symlinks-flag": "chmod -R a+X *",
"strip-final-newline": "chmod -R a+X *",
"webpack-dev-server": "chmod -R a+X *",
"tapable": "chmod -R a+X *",
"statuses": "chmod -R a+X *",
"@nivo/legends": "chmod -R a+X *",
"@lingui/react": "chmod -R a+X *",
"license-webpack-plugin": "chmod -R a+X *",
"command-exists-promise": "chmod -R a+X *",
},
Some npm packages have malformed tarballs (missing the +x file attr bit on directories) which don't play nicely with Bazel when they are extracted by the rules_js
NpmPackageExtract
action. See https://github.com/aspect-build/rules_js/issues/1637 for more details.An example error from this issue:
The work-around for these npm packages is to add
custom_postinstall
scripts for each withchmod -R a+X *
orchmod -R a+X * && <other custom postinstall steps>
to thenpm_translate_lock
repository rule / bzlmod extension.This issue is here for users to share all of the package that this problem has been observed on where this work-around may be needed.