internalBinding is not defined


#1

my project, koleotank-arrasio-master2.glitch.me was working well until today.
apparently, today it broke, and i can’t do anything to fix it.

internal/util/inspect.js:31
12:44 PM
const types = internalBinding('types');
12:44 PM
^
12:44 PM
12:44 PM
ReferenceError: internalBinding is not defined
12:44 PM
at internal/util/inspect.js:31:15
12:44 PM
at req_ (/rbd/pnpm-volume/241b0011-fb7f-4aae-8481-17d632cc5615/node_modules/.registry.npmjs.org/natives/1.1.4/node_modules/natives/index.js:137:5)
12:44 PM
at require (/rbd/pnpm-volume/241b0011-fb7f-4aae-8481-17d632cc5615/node_modules/.registry.npmjs.org/natives/1.1.4/node_modules/natives/index.js:110:12)
12:44 PM
at util.js:25:21

12:44 PM
at req_ (/rbd/pnpm-volume/241b0011-fb7f-4aae-8481-17d632cc5615/node_modules/.registry.npmjs.org/natives/1.1.4/node_modules/natives/index.js:137:5)
12:44 PM
at require (/rbd/pnpm-volume/241b0011-fb7f-4aae-8481-17d632cc5615/node_modules/.registry.npmjs.org/natives/1.1.4/node_modules/natives/index.js:110:12)
12:44 PM
at fs.js:42:21
12:44 PM
at req_ (/rbd/pnpm-volume/241b0011-fb7f-4aae-8481-17d632cc5615/node_modules/.registry.npmjs.org/natives/1.1.4/node_modules/natives/index.js:137:5)
12:44 PM
at Object.req [as require] (/rbd/pnpm-volume/241b0011-fb7f-4aae-8481-17d632cc5615/node_modules/.registry.npmjs.org/natives/1.1.4/node_modules/natives/index.js:54:10)
12:44 PM
at Object.<anonymous> (/rbd/pnpm-volume/241b0011-fb7f-4aae-8481-17d632cc5615/node_modules/.registry.npmjs.org/graceful-fs/3.0.11/node_modules/graceful-fs/fs.js:1:99)

please help, thank you.


#2

Hi :slight_smile:

sorry about it! It looks like some of your packages is using an old version of the package natives… I tried to update it but it didn’t get applied, because it’s an internal dependency… Do you mind if I poke in the project dependencies a bit to figure out what’s going on?

PS: in case you are wondering, I am part of Glitch support :wink:


#3

FYI: I have the same poblem with a completely different project. It happened after upgrading to node 10


#4

Thank you for this info! Then probably going back to Node 8 should fix it. You can see that I added a section in package.json specifying the node version you want. You can do it in your other project too.