Validate everything works locally: npm run validatenpm run dev
Create a new github repo
Add AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to your GitHub repo's secrets. Go to your AWS security credentials and click on the "Access keys" tab, and then click "Create New Access Key", then you can copy those and add them to your repo's secrets.
2023-09-23T20:08:57.792Z da801d89-8960-42c2-b45e-c3f84c59da2a ERROR Invoke Error {
"errorType": "ReferenceError",
"errorMessage": "Request is not defined",
"stack": [
"ReferenceError: Request is not defined",
" at createRemixRequest (/var/task/node_modules/@remix-run/architect/dist/server.js:53:3)",
" at Runtime.handler (/var/task/node_modules/@remix-run/architect/dist/server.js:37:19)",
" at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1147:29)"
]
}
Expected Behavior
Application should be deployed and display output at the endpoint from the production deploy.
Actual Behavior
Error at the production url:
{"message":"Internal Server Error"}
Error in cloudwatch logs:
2023-09-23T20:08:57.792Z da801d89-8960-42c2-b45e-c3f84c59da2a ERROR Invoke Error {
"errorType": "ReferenceError",
"errorMessage": "Request is not defined",
"stack": [
"ReferenceError: Request is not defined",
" at createRemixRequest (/var/task/node_modules/@remix-run/architect/dist/server.js:53:3)",
" at Runtime.handler (/var/task/node_modules/@remix-run/architect/dist/server.js:37:19)",
" at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1147:29)"
]
}
Have you experienced this bug with the latest version of the template?
yes
Steps to Reproduce
Following the readme step for step:
npx create-remix@latest --template remix-run/grunge-stack
npm run validate
npm run dev
Expected Behavior
Application should be deployed and display output at the endpoint from the production deploy.
Actual Behavior
Error at the production url:
Error in cloudwatch logs: