ehmicky
ehmicky
Thanks @CanRau. This means this is not a problem related to the `js-client` but to our API. I am forwarding this to our API team. @vbrown608 @kitop @keiko713 Do you...
Hi @styxlab, Thanks a lot for point that out! Reducing the bundle size is definitely a good thing. I would recommend using a tool like [source-map-explorer](https://github.com/danvk/source-map-explorer/) for diagnosing this. ...
This is a much better name. Using `npm deprecate`, users would get notified to update the package name. However, some users will skip this warning and get stuck on an...
We should coordinate with the documentation team @rstavchansky to check if anything should be changed there.
Hi @riddla UMD builds are currently [experimental](https://github.com/netlify/js-client#umd-builds) and are unfortunately not working quite yet. In your case, it seems like Webpack might be tripping up on the `...` spread operator....
Yes sorry, that makes sense. Thanks!
Same here. It used to work, but it does not anymore.
I think the `discriminator` property might be involved in this as well. See #61
An additional use case for it would be to clean up CLI spinners or progress bars.
Node 10 is now out and supports Unicode property escapes and named groups. Negative lookbehind assertions were actually already supported in Node 9.