-
Notifications
You must be signed in to change notification settings - Fork 13
[Fix] fix "exports" for node 13.0-13.6 #41
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
Conversation
- node 13.0-13.1 only supports the string form - node 13.2 - 13.6 in an object only supports "default" This commit allows these node versions to work.
cc @goto-bus-stop :-) |
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.
lgtm, i dont have perms here though 😄
oh noes! cc @twada |
ping @twada |
From the support-policy
Thus I don't think this PR will be getting merged. Node 13 isn't in LTS and Node 14 is going to be leaving LTS in a month. |
@RebeccaStevens Support policy is irrelevant; Patching installed modules live is FAR worse than forking them, ftr. |
ping @twada; this is continuing to cause failures in some of my projects' CI, and i'd love it to be fixed. I'd be more than happy to help you maintain this package if you're short on time! |
@ljharb Thank you for pinging me! I've been sick and absent recently, but will be rebooting now! |
<3 thank you! glad you're feeling better :-) |
This is reasonable. |
unassert 2.0.1 is out. Thank you @ljharb ! |
This commit allows these node versions to work.