npm start throwing error status 1 require is not a function

Question

I get the following error when running npm start.

> app@0.1.0 start /Users/user/Desktop/react-tutorial
> react-scripts start

require(...) is not a function
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! app@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the app@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

Here is the actual error

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm@6.4.1
3 info using node@v10.15.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle app@0.1.0~prestart: app@0.1.0
6 info lifecycle app@0.1.0~start: app@0.1.0
7 verbose lifecycle app@0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle app@0.1.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/user/Desktop/react-tutorial/node_modules/.bin:/Library/Java/JavaVirtualMachines/jdk-9.0.4.jdk/Contents/Home/bin:/Users/user/Library/Android/sdk/tools:/Users/user/Library/Android/sdk/platform-tools:/Library/Frameworks/Python.framework/Versions/3.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Xamarin Workbooks.app/Contents/SharedSupport/path-bin:/opt/local/share/java/android-sdk-macosx/platform-tools:/Users/user/.android-sdk-macosx/platform-tools/:/Users/user/.android-sdk-macosx/platform-tools/:/Users/user/Library/Android/sdk/platform-tools/
9 verbose lifecycle app@0.1.0~start: CWD: /Users/user/Desktop/react-tutorial
10 silly lifecycle app@0.1.0~start: Args: [ '-c', 'react-scripts start' ]
11 silly lifecycle app@0.1.0~start: Returned: code: 1  signal: null
12 info lifecycle app@0.1.0~start: Failed to exec start script
13 verbose stack Error: app@0.1.0 start: `react-scripts start`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:962:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid app@0.1.0
15 verbose cwd /Users/user/Desktop/react-tutorial
16 verbose Darwin 16.7.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v10.15.0
19 verbose npm  v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error app@0.1.0 start: `react-scripts start`
22 error Exit status 1
23 error Failed at the app@0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

This just started to happen when i restarted computer...why

I can't find anywhere where I am calling require()... maybe a plugin I installed?

Possible duplicate of [NodeJs : TypeError: require(...) is not a function](https://stackoverflow.com/questions/33007878/nodejs-typeerror-require-is-not-a-function) — T04435, Mar 25 '19 at 23:37
I am getting the exact same error. just happened out of nowhere... did you find a solution? — AKrush95, Apr 01 '19 at 05:11
Try the answer below. When I tried it, it didn't work. When I got into work, I tried it again and then it worked. — letsCode, Apr 01 '19 at 07:36
if you have created any file like setupProxy.js in root level, you can delete that file and run npm start — Srinivas, Jan 29 '20 at 12:24

score 4 · Answer 1 · answered Nov 29 '20 at 11:06

In my case, had created a setupProxy.js file at project level, later i removed the configurations in it but not the file. Hence the mentioned error in question was thrown. To resolve, try one of the following according to your need,

update the proper configuration in the setupProxy.js
delete the setupProxy.js if not needed
don't leave the setupProxy.js as empty file

score 1 · Answer 2 · answered Mar 26 '19 at 00:21

1

Delete nodes_modules
npm install -g npm
npm install & npm install -D
npm run start

answered Mar 26 '19 at 00:21

CraftyMonkey

395
1
6

score 1 · Answer 3 · answered Jan 19 '21 at 21:50

Thanks to @Srinivas's response in the comment of the question.

Delete the generated setupProxy.js file. If you want to use a proxy, instead add it into your package.json file.

  "proxy": "http://localhost:3000",

For a setupProxy.js file like so:

const proxy = require('http-proxy-middleware');

// tells the browser to direct any relative reference paths to the below 
// domain instead of our own
module.exports = function(app) {
  app.use(proxy('/api/*', { target: 'http://localhost:3000' }));*/
};

score 1 · Answer 4 · answered Aug 19 '21 at 19:20

When you are setting up a Proxy to make a request to a different server

First Step is to install the dependency

npm install --save http-proxy-middleware

Next create setupProxy.js file

setupProxy.js

const { createProxyMiddleware } = require('http-proxy-middleware');

module.exports = function(app) {
  app.use(
    '/api',
    createProxyMiddleware({
       target: 'http://localhost:3001',
       changeOrigin: true
    })
  );
};

npm start throwing error status 1 require is not a function

4 Answers4