-
Notifications
You must be signed in to change notification settings - Fork 89
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
version 1.1.0 got error in node 8.12.0 #112
Comments
I have also been facing this issue. |
@hzxulin what version of node? |
This comment has been minimized.
This comment has been minimized.
node 8.12.0 npm 6.4.1 |
@mosquito1803 @hzxulin can you try node 10? Node.js 8.x Maintenance LTS cycle expired December 31, 2019 and is pretty out of date. |
@lazd But I need to use the Node 8 version for my project. Can you change the package version to 2.0.0 |
@mosquito1803 @hzxulin can you try adding the following to your
if that doesn't work, try 3.0, then 2.0. etc.
|
@lazd Changing node version and |
@lazd This requires modification of our project package.json file. We have hundreds of such projects, and it is very difficult for me to do this |
@hzxulin @mosquito1803 testing with |
@hzxulin @mosquito1803 try |
@lazd It worked. Thank you very much ! ❤ |
@hzxulin you're welcome! Thanks for reporting and sorry for the headaches caused. I added testing for node back to version 8 to avoid issues like this in the future. I realize this is a widely used package and should support even the oldest node versions if possible, but still urge you to upgrade to a later version as soon as you can. If not for security, |
Thanks, it works here too! Next time you want to abandon node 8, just help youself to update the package to 2.0.0. |
@mosquito1803 TBH I had no idea node 8 would break because I wasn't testing on it, but now I am! |
It's true, node 8 should be out of date that we are using node 8 only in some old projects. Thanks again for your help! |
We are using gulp-replace in node 8.12.0, verison 1.0.0 goes well but after version 1.1.0 release it got error then. The error log is placed below.
The text was updated successfully, but these errors were encountered: