Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

83
Views
Namespace 'NodeJS' has no exported member 'Require'

I'm new in Electron.. and i just following this guide: https://www.geeksforgeeks.org/integrate-angular-7-with-electronjs/?ref=rp

but, i don't know why, i can't continue the step 4, on accessing the electron, and keep popping this when doing build or even just serve.

Error: node_modules/electron/electron.d.ts:6594:21 - error TS2694: Namespace 'NodeJS' has no exported member 'Require'.

6594 require: NodeJS.Require; ~~~~~~~

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! pemberkasan@0.2.0 electron: ng build --prod && electron . npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the pemberkasan@0.2.0 electron script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

i hope anyone here, understand with this and able to solve this. thank you! because my goal is to connect ipcMain, using ipcRenderer that i triggered on Angular Services.

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

Try these two steps:

  1. Delete the node_modules folder and run

$ npm install

  1. If this doesn't work, it might be to do with an outdated @types/node dependency. Try running:

$ npm update @types/node

over 4 years ago · Santiago Trujillo Report

0

I believe this problem happened because of an old version of @types/node, as Angular uses TypeScript as its backbone.

npm update itself wouldn't work if the update is a breaking change.

In order to fix this, update your package.json to use the latest version of @types/node, at this time of writing 14.14.33. You can update it manually by editing that file.

After updating your @types/node, run npm install again, then serve it, and it should work.

If it still fails, update your Angular CLI to the latest version by using npm uninstall -g @angular/cli, then npm install -g @angular/cli. You might be using an outdated Angular CLI.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!