-
Notifications
You must be signed in to change notification settings - Fork 130
Conversation
Note: I've modified some tests in order to use higher versions of some packages.
🤘 |
Is there anything that needs doing before this PR can be accepted? I'm happy to help, as I'd like to use Myth under Node v6! |
Node 6 should be added to If that passes I would happily merge this, but I'm not an owner of the npm package... one of the owners would need to be pinged to publish a new release. |
cc npm package owners: @dominicbarnes, @MoOx, @ianstormtaylor I tried to come up with a one-liner to collect the github handles of the npm package owners, but I fell short. I got this far:
I thought I could pipe that to |
FYI, I am now the maintainer of a project that achieve the same goal called cssnext based on another engine (postcss). This projects support way more features and works in various versions of node ;) |
@MoOx Looks awesome! I think I'll use that instead then :-) |
And @zeke, I think you want the npm i -g npm-user-cli && npm owner ls myth | cut -d' ' -f1 | xargs -I {} npm-user {} That limits it to 1 item per run of the command. Alternatively, you could do |
Any particular reason for closing this @pin3da? Leaving a comment would be really helpful. It's confusing when a PR gets closed for seemingly no reason with no explanation :-/ |
Sorry for closing it without any comment ): The main reason is I was cleaning some open PRs, and this one did not have any activity in the last years. Also, I haven't been involved with nodejs in a while. If there is still an interest/need on it, I can open it again and fix what is necessary. |
It should solve #137 , #138 and #142