b-bot

@kyeotic the message seems to be a false negative. I think the word 'not' is an error because as noted above - the package is still published with the new...

Why is this closed? Still experiencing this in the latest version.

Any solution to this? The above workaround is not working with the Modal `Header`, `Body` and `Footer` unfortunately.

@tianenpang Thanks for the help, unfortunately I am getting the same error. However this does mean that it is likely more to do with the `styled` export. I should probably...

Hi @jrgarciadev - again the same error, I have tried this import before. Likely not related to your library as it is present in Stitches but this issue seems to...

@overheadhunter yeah it's just the convenience aspect that makes it an attractive feature. I prefer to manually enter my password every time because if I choose to remember password that...

> If I've learned one thing about Next.js throughout my time deploying with Amplify, it's that Next.js has no qualms with breaking deployment behaviour that external services depend on between...

@ucjallen thanks for this tip was wondering how to do it and wanted to stay in the confines of the amplify ecosystem. there should DEFINTELY be a callback function that...

This can be fixed by adding the fonts to the public folder in the project root as the source needs to be absolute. ie. expose it at `https://react-pdf.org/Roboto-Regular.ttf`

I think we should escape all of these invisible characters for better compatibility with packages. Like @chan-vince I also ran into issues when using Cognito lambda triggers as it violates...