Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReferenceError: primordials is not defined #877

Open
amejiarosario opened this issue Jun 9, 2019 · 1 comment
Open

ReferenceError: primordials is not defined #877

amejiarosario opened this issue Jun 9, 2019 · 1 comment

Comments

@amejiarosario
Copy link

Using node 12 and gulp 3. That combination does not work: gulpjs/gulp#2324

$ npm run build

> kickstart@ build /Users/admejiar/Code/tmp/ampstart
> gulp build

fs.js:27
const { Math, Object } = primordials;
                         ^

ReferenceError: primordials is not defined
    at fs.js:27:26

I tried gulp 4 and getting different errors

@ghost ghost mentioned this issue Jun 24, 2019
@ghost
Copy link

ghost commented Jun 24, 2019

Regarding the Node version: the engines section of the package.json specifies that Node version ^7.0.0 is required. The caret (^) allows changes that do not modify the left-most non-zero digit in the [major, minor, patch] tuple. Therefore, the highest version one should use is v7.10.1. You'll need to use NVM or NVM for Windows to switch versions and build as intended.

Regarding the Gulp version: the devDependencies section of the package.json specifies that Gulp version ^3.9.1 is required. One should use the locally-installed version of Gulp rather than the global installation. Having a different version of Gulp installed globally may interfere with using the locally installed one. The global installation should probably be uninstalled.

From what I saw from other bug reports, "ReferenceError: primordials is not defined" seems to primarily affect Windows users. Even with the correct versions of the above, additional bugs are present on Windows 10. @amejiarosario, if you are on Windows 10, you will need to wait for #878 to be merged before npm i and npm run build will complete smoothly. Feel free to clone and use my fork in the mean time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant