-
Notifications
You must be signed in to change notification settings - Fork 628
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
Request: publish new version of npm package #941
Comments
This makes sense to me - I have merged some PRs and updated the changelog in preparation for this. But I'm wondering about fixing e.g. the typescript bits before pushing another release. There are some other open PRs as well, unfortunately some need significant reviewing/rebasing and/or fixing up to merge, which is a bit unfortunate. I'm also going to have to take a health break for a bit starting tomorrow. Will let the other maintainers know if I take too long to get back. If you get a chance to submit a PR for the typescript stuff (I tried to investigate but got pretty confused because it seems typescript 1 and 2 treat null values for typed properties differently?) then I'd be happy to try to get that merged. |
Thanks @gijsk, I appreciate all your help. Please don't feel any time pressure from me. I'll get a PR up for the TypeScript tweak in the new few days. |
Hi folks - would love to get a new version published to get some of the fixes into the live version (instead of the patch dependency we're using internally at the moment). Anything I can help with to unblock a release? |
See #936 (comment) and #933 (comment)
The text was updated successfully, but these errors were encountered: