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

Issues with Node v8 compatibility in new release #158

Open
ethan-arreya opened this issue Sep 11, 2024 · 0 comments
Open

Issues with Node v8 compatibility in new release #158

ethan-arreya opened this issue Sep 11, 2024 · 0 comments

Comments

@ethan-arreya
Copy link

Upon installing [email protected] into our Node 8 project we were getting errors with running Grunt. The v8flags dependency changed from ~3.2.0 to 4.0.

0.613 /usr/local/lib/node_modules/grunt-cli/node_modules/v8flags/index.js:84
0.613   var flags = Array.from(process.allowedNodeEnvironmentFlags);
0.613                     ^
0.613 
0.613 TypeError: Cannot convert undefined or null to object
0.613     at Function.from (native)
0.613     at getFlags (/usr/local/lib/node_modules/grunt-cli/node_modules/v8flags/index.js:84:21)
0.613     at /usr/local/lib/node_modules/grunt-cli/node_modules/v8flags/index.js:142:5
0.613     at /usr/local/lib/node_module...

They invoke process.allowedNodeEnvironmentFlags which wasn't introduced into Node until v10.10. If we attempt to set NODE_OPTIONS to circumvent the errors, the object on the process variable wouldn't exist .

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