Travis Martin

I did some testing and have discovered that three aspects of my code were causing the build error. The "static" keyword: ```js class Foo { static bar = 0; }...

The package I linked in the original example has been renamed and changes were made within the code so that it would bundle correctly. It would still be nice for...

It seems like the [nullish coalescing operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing_operator): ```js const foo = (bar) => bar ?? 0; ``` and [optional chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining): ```js foo?.bar?.(); ``` also cause build errors. Both are also...

Adding onto this because it's somewhat related. Is there currently no way to use `MDXProvider`'s custom components without client-side rendering? It seems a little bit silly that I would need...

> I've been experiencing the same thing- I think this issue has something to do with SSL certs from CA's that are too new. Is there a list of what...

> > When I asked about this in the developer Discord they suggested I just don't use SSL at all for best results. > > I opened a support ticket...