xeogl icon indicating copy to clipboard operation
xeogl copied to clipboard

Error when running npm run build

Open TjalleWired opened this issue 5 years ago • 4 comments

Describe the bug Error when trying to build the project using npm run build

A clear and concise description of what the bug is. Log of when error appears; 2020-05-28T09_48_42_493Z-debug.log

To Reproduce Run everything with elevated user perms.

use git to clone latest repo run npm install ,which yields the expected results. npm run build give out an error.

fs.js:35
} = primordials;
    ^

ReferenceError: primordials is not defined
    at fs.js:35:5
    at req_ (/mnt/c/Users/admin/Desktop/xeogl/xeogl/node_modules/natives/index.js:143:24)
    at Object.req [as require] (/mnt/c/Users/admin/Desktop/xeogl/xeogl/node_modules/natives/index.js:55:10)
    at Object.<anonymous> (/mnt/c/Users/admin/Desktop/xeogl/xeogl/node_modules/graceful-fs/fs.js:1:37)
    at Module._compile (internal/modules/cjs/loader.js:1133:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
    at Module.load (internal/modules/cjs/loader.js:977:32)
    at Function.Module._load (internal/modules/cjs/loader.js:877:14)
    at Module.require (internal/modules/cjs/loader.js:1019:19)
    at require (internal/modules/cjs/helpers.js:77:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `gulp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.


Expected behavior A succesfull build using npm run

Desktop (please complete the following information):

  • OS: Windows 10 Latest stable release, NPM v6.14.4, Node v12.16.3

Additional context Also have tried using WSL Ubuntu and Ubuntu 18.04 LTS

TjalleWired avatar May 28 '20 09:05 TjalleWired

It seems that the error is in a gulp version mismatch. Not entirely sure yet.

Also have tried downgrading to current LTS node version (12.17)

TjalleWired avatar May 28 '20 09:05 TjalleWired

I miss a same problem. Have you solve it yet?

moriarty233 avatar May 29 '20 09:05 moriarty233

I miss a same problem. Have you solve it yet?

Not yet. I will post my fix, IF I ever find it . I suggest you do the same ;)

Problem seems to be in the versions of the packages.

TjalleWired avatar May 29 '20 09:05 TjalleWired

I find a solution. https://stackoverflow.com/questions/55921442/how-to-fix-referenceerror-primordials-is-not-defined-in-node

moriarty233 avatar Jun 07 '20 04:06 moriarty233