-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix for Node v14 'Accessing non-existent property' errors #2538
Conversation
I tested the patch it and it worked. I was getting the warning messages from using |
All confirmed this solves the issue for me. |
Patch works for me, thanks! |
Another confirmation that the patch works -- can't wait for it to be merged so I can get rid of those pesky little warnings! |
tested this patch on node v14.4.0 and this fixes the issue. Any update on when this will be merged? |
@xdan @dtvn PLEASE merge and release this patch so I don't have to do horrible things like this 😫 https://github.com/slightlyfaulty/stylus-native-loader#stylus-warnings-since-node-v14 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please 😄
@xdan Please also update nib's dependency, it still uses old stylus. Thanks. |
@willbarkoff this hopefully fixes the issues with node v14 see stylus/stylus#2538
Fix for Node v14 'Accessing non-existent property' errors stylus#2538
Fix for issue #2534
Why it happens
lib/nodes/index.js
performsnew exports.Boolean(true)
which readsnodes.lineno
. Sincelineno
is missing inlib/nodes
, node.js outputs warnings. Same is for propertiescolumn
andfilename
.How to reproduce
With node v14:
It will output
1. Make sure you have tests for your modifications.
Are tests needed for this fix? If so what should they check?