Jared Franzone

Hi, yes this is a bug and we are working on a fix. As a temporary workaround you can manually add the environment variable to your SSR Lambda function in...

Hi all! We have added support for Environment variables for Next.js SSR apps. Follow these steps to enable: 1. Add your desired environment variable in the Amplify Console like normal...

> I was just thinking, nextjs has public and private env variables, some that get sent to the client start with NEXT_PUBLIC_, how are they treated now? will env. variables...

> @Athena96 I'm having issues now with my production build. It's not taking the env. overrides and always picking the default sets for the variables. > > Could you please...

Hi @RealDrewKlayman , sorry you are facing this. We have identified an issue with how we bundle modules with newer versions of webpack5 and Next.js for the server side lambdas....

### Webpack / Cannot find Module / ModuleNotFound / NotImplemented Hi @RealDrewKlayman and others, If you are facing Webpack errors (Cannot find module/ ModuleNotFound) as a result of the new...

Hello! Please try following both the "**Install the Amplify GitHub App in your account**" and "**Generate a personal access token in your GitHub account**" steps [here](https://docs.aws.amazon.com/amplify/latest/userguide/setting-up-GitHub-access.html#setting-up-github-app-cloudformation)

Hi @vishalvishalgupta this is currently not supported, but checkout [this issue](https://github.com/aws-amplify/amplify-cli/issues/1484) which describes a workaround using git tags.

Hi @belgac, thank for reaching out! Currently reopening a closed PR will not start a new build. A workaround would be to duplicate the PR you wanted to re-open. I'll...