Build exceeds memory limits?

how can i overcome this issue?

9:39:23 PM: Caching artifacts

9:39:23 PM: Started saving node modules

9:39:23 PM: Finished saving node modules

9:39:23 PM: Started saving build plugins

9:39:23 PM: Finished saving build plugins

9:39:23 PM: Started saving yarn cache

9:39:25 PM: > the_stripes_nft_dapp@1.0.0 build

9:39:25 PM: > npm run build

9:39:26 PM: > the_stripes_nft_dapp@1.0.0 build

9:39:26 PM: > npm run build

9:39:28 PM: > the_stripes_nft_dapp@1.0.0 build

9:39:28 PM: > npm run build

9:39:34 PM: > the_stripes_nft_dapp@1.0.0 build

9:39:34 PM: > npm run build

9:39:48 PM: > the_stripes_nft_dapp@1.0.0 build

9:39:48 PM: > npm run build

9:40:45 PM: Build exceeded memory limits

is it normal to say npm run build a good 500 times?

There is something wrong with your build settings and build script @ItsDave

Can you share the build settings you are using and the build script from your package.json

{

β€œname”: β€œthe_stripes_nft_dapp”,

β€œversion”: β€œ1.0.0”,

β€œdescription”: β€œThe Stripes NFT minting dapp is a quick and easy way to connect your smart contract and start minting NFTs.”,

β€œprivate”: true,

β€œdependencies”: {

"node-fetch": "^2.6.7",

"react": "^17.0.2",

"react-dom": "^17.0.2",

"react-redux": "^7.2.4",

"react-scripts": "4.0.3",

"redux": "^4.1.1",

"redux-thunk": "^2.3.0",

"styled-components": "^5.3.0",

"web-vitals": "^1.0.1",

"web3": "^1.5.1",

"web3-eth-contract": "^1.5.2"

},

β€œauthor”: β€œAli Solanki, Daniel Eugene Botha”,

β€œlicense”: β€œMIT”,

β€œscripts”: {

"start": "react-scripts --openssl-legacy-provider start",

"build": "CI= npm run build"

},

β€œbrowserslist”: {

"production": [

  ">0.2%",

  "not dead",

  "not op_mini all"

],

"development": [

  "last 1 chrome version",

  "last 1 firefox version",

  "last 1 safari version"

]

}

}

When you run npm run build, npm executes the command under the scripts > build.

What you have here is a command that is calling itself repeatedly.

sorry to be a complete noob what is the fix for this?

Have you looked at the Create React App documentation or Netlify’s documentation?

You need

scripts: {
  "build": "react-scripts build"
}

Then npm run build as the build command in the UI.

Legend much lovemuch appreciated

​this is the new drama in my night any ideas?
11:17:23 PM: ────────────────────────────────────────────────────────────────
11:17:23 PM: β€œbuild.command” failed
11:17:23 PM: ────────────────────────────────────────────────────────────────
11:17:23 PM: ​
11:17:23 PM: Error message
11:17:23 PM: Command failed with exit code 254: npm run build
11:17:23 PM: ​
11:17:23 PM: Error location
11:17:23 PM: In Build command from Netlify app:
11:17:23 PM: npm run build
11:17:23 PM: ​
11:17:23 PM: Resolved config
11:17:23 PM: build:
11:17:23 PM: base: /opt/build/repo
11:17:23 PM: command: npm run build
11:17:23 PM: commandOrigin: ui
11:17:23 PM: environment:
11:17:23 PM: - ONEGRAPH_AUTHLIFY_TOKEN
11:17:23 PM: publish: /opt/build/repo/build

This is the same issue you had previously Issue deploying website build command fauiled:Command failed with exit code 254: npm run build the solution to which was to change the base directory I believe.

If this does not work, you will need to share a public repository.

still no good NftItsDave is now public, all your help is much appreciated from a beginner

https://github.com/lemmo-bit/It-s-DaveNFT1 is not public

NftItsDave is the name of the one i am currently using

Can you provide the link please

absolutely thank you for your time mate GitHub - lemmo-bit/NftItsDave

In your previous thread I suggested searching the forums for nft-minting-app-main as there are multiple threads involving Stripes NFT which all have solutions.

I have already provided the solution to your issue:

The Stripes NFT app is inside the nft-minting-app-main directory inside your repository. You need to set the base directory in the UI to nft-minting-app-main like this:

Edited: to fix error in screenshot.

this was what i did when i got the memory error, thanks again and sorry

Hey @ItsDave

But the build script (as explained above) was calling itself, and that you should change it i.e.

1 Like