Hello,
It looks like even after the fix in webpack-asset-relocator-loader@1.2.3 to handle properly @mapbox/node-pre-gyp ncc is still not able to relocate bcrypt@5.0.1.
I ran some tests by building locally ncc:
ncc@82bffab1df2c8936e1151352889a73434fd45dc4 (0.28.0 tag) - bcrypt correctly relocated ✅
ncc@00cdc3f31a455dfa14c86f85c622776a31ab5ee2 (update to webpack-asset-relocator-loader@1.2.3) - bcrypt correctly relocated ✅
ncc@446fc5645141fd119c120c766e33051bb3a4935b (before fix of webpack-asset-relocator-loader) - bcrypt not relocated 🔴
But when I use the npm:@vercel/ncc@0.28.0 bcrypt is not relocated so I think there is an issue with packaged version.
Hello,
It looks like even after the fix in
webpack-asset-relocator-loader@1.2.3to handle properly@mapbox/node-pre-gypncc is still not able to relocatebcrypt@5.0.1.I ran some tests by building locally ncc:
ncc@82bffab1df2c8936e1151352889a73434fd45dc4 (0.28.0 tag) - bcrypt correctly relocated ✅
ncc@00cdc3f31a455dfa14c86f85c622776a31ab5ee2 (update to
webpack-asset-relocator-loader@1.2.3) - bcrypt correctly relocated ✅ncc@446fc5645141fd119c120c766e33051bb3a4935b (before fix of webpack-asset-relocator-loader) - bcrypt not relocated 🔴
But when I use the
npm:@vercel/ncc@0.28.0bcrypt is not relocated so I think there is an issue with packaged version.