highly annoying. Works super on my local, but can’t deploy. This function it complains of used to get build two months ago until last week. So this happened with some Netlfy update. Error: In file "/opt/build/repo/functions/create-user.js": Cannot find module 'encoding' Require stack: 2:03:42 PM: …

thanks @Scott for your input. The solution some had in the linked disussion, did not help me (encoded as dependency) Also, something useful was in cache and now there is no cache. What helps here? Seems like problem is with npm versions to me, but can’t really affect this

This can happen is cached versions all work in harmony and then the cache is dropped. Have you considered the following points from that topic? Added “encoding” to package.json Worked for me. NB! Had to remove package-lock as well But npm install encoding and then rebuilding worked.

I have installed encoding as a dependency and no luck with removing package-lock

That error usually crops up when using node-fetch. It doesn’t do it often anymore but the simplest solution is to switch the package for isomorphic-fetch. The good thing is the syntax/api for is the same so it just a matter of changing the require statement. Let me know if that helps.

I don’t use node-fetch at all

Hey @Mik-A , Really sorry to have dropped the ball here! For quicker response times going forward, please open a ticket in our helpdesk by emailing support@netlify.com from an email address associated with your Pro account and we’ll get back to you there. For now, we did take a look at your deploys…

hmm, not sure where to change as per your suggestion. Toml has “npm run build” and package.json has that too. However. I don’t know how to link my local folder with netlify. it asks for an ID but there is no such things. if I use netlify link -name my-site-name’ It looks for something in github an…

Sorry for that slow followup; Jen’s been out. What she was saying is you’ll want to change the command in the toml from what it is now to: npm run build ; cat /opt/buildhome/.npm/_logs/2020*debug.log ; sleep 300 ; false and that should show the npm error log in the deploy logs to help you diagno…

ok i get it it now. However did not find anything new there. But found out that Netlify updates seem to have stopped supporting a few npm packages. google-spreadsheet googleapis firebase-admin at least when used in lambda functions with netlify-cli

Deploy failed due to an error in @netlify/plugin-functions-core plugin

Support

Scott October 28, 2020, 11:09pm 2

Quite likely, something useful was cached and, well… now there’s no cache!

There’s a hearty discussion over here – hopefully this steers you in the right direction

Topic		Replies	Views
Plugin "@netlify/plugin-functions-core" internal error Support building , lambda-functions	15	1721	November 12, 2020
A Netlify Function failed to require one of its dependencies Support building , deployment	13	1182	October 10, 2023
Error: Could not find “encoding” module in file, Netlify function Support lambda-functions	25	8820	February 17, 2026
How to include dependencies in Netlify Lambda Functions? Support lambda-functions	33	19762	July 27, 2020
Failed during stage 'preparing site for deployment': exit status 1 Support	8	3455	July 30, 2019

Deploy failed due to an error in @netlify/plugin-functions-core plugin

Related topics