Skip to content

Conversation

@immartian
Copy link

some issues including #1411 are all related to unsupported gulp v3.x, so changed the least version to v4.0.0 to assure the binding of several packages including Prism and Node-sass.

tested on both node v11.x and v12.x.

@immartian
Copy link
Author

Without this change, the current code base will not be able to run, most probably showing such errors:

Aborted
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] postinstall: `gulp build-prism`
npm ERR! Exit status 134
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

@ProbablyFaiz
Copy link

+1, this fixed my local instance which was previously showing that 134 code you posted above.

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

Successfully merging this pull request may close these issues.

2 participants