Open parsibox opened 2 years ago
Similar issue here on windows 10. Have you found the solution? Why the node-v93-win32-x64-unknown?
no
Sir, in the meantime I've found the solution for my specific case (probably it has nothing to do with yours though, sorry). In my case I have 1) a rough final solution 2) a quick analysis of the issue. Fyi 1) in my react app, it was due to firebase analytics the need of grpc causing my issue, hence as a very rough solution I deleted the firebase wrapper (just a couple of lines in the app js) of the react app (atm not needed in my dev) and I "solved" my issue 2) I think the original problem (after a misleading certificate error resolved with a node env var setting to ignore it) was a 404 not found due to an "unknown" final part in the URL. My wild guess is that it is due to a missing/incomplete setup of c++ win node-gyp sdk... Which appears to be a little problematic, in my case it was not a priority and I adopted point 1)
I've shared my latest gist comment in my profile (fwiw) https://gist.github.com/giuliohome/f8612fc663225d49be79296302c03ff6?permalink_comment_id=4313263#gistcomment-4313263
windows 11 64 bit node -v v16.13.2 node-pre-gyp -v v0.13.0