Closed jca41 closed 2 years ago
Do you use yarn
? Did you try to remove node_modules
and reinstall everything with npm i
?
I do use yarn, I'll try with npm and let you know!
Moved to npm
and added a package-lock to the project, issue still persists for both node 16 and 14.5.
The "problem" is that it works fine locally but breaks when deploying to vercel. Vercel is using node 14.x apparently.
re2
is a C++ module that should be compiled. Do you have a C++ compiler installed as per node-gyp
requirements? If re2
fails to download a precompiled version it reverts to compiling sources. Could you check that it doesn't fail?
07:20:07.675 | > node-gyp-build
-- | --
07:20:07.884 | > re2@1.16.0 install /vercel/path0/node_modules/re2
07:20:07.884 | > install-from-cache --artifact build/Release/re2.node --host-var RE2_DOWNLOAD_MIRROR \|\| npm run rebuild
07:20:07.992 | Trying https://github.com/uhop/node-re2/releases/download/1.16.0/linux-x64-83.br ...
07:20:08.264 | Writing to build/Release/re2.node ...
07:20:08.737 | Done.
I get this from the deployment logs. Probably the best step for now is to get a minimal reproduction and ask the Vercel/Next.js team.
Hmm. It looks like the module was found and downloaded. Then it runs a check to make sure that everything is working as expected. I don't see any errors. If it was downloaded but not working, it will compile the module. I don't see it was needed.
I hope that the lack of updates means that you sorted it out. Please reopen, if you still need my help.
Hey! I kind of gave up on the issue and decided not to upgrade to next 12 for now. Thanks anyways!
Hi! After upgrading to next.js 12 i now get the following error:
I'm originally using this package via
metascraper