aws-amplify / aws-amplify/amplify-hosting

Support for remix framework

Open
#3,344 2 comments 9 reactions 0 assignees View on GitHub
feature-request framework frontend-builds
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

NEW_APP

### AWS Region

us-east-1

### Amplify Hosting feature

Frontend builds

### Is your feature request related to a problem? Please describe:

I'm not able to deploy a [remix](https://remix.run/) app to Amplify.

Not sure if I can manually edit the build settings to get around this though?

### Describe how you'd like this feature to work

Allow for remix framework apps to be deployed as easily as NextJS apps.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing Amplify Hosting's frontend build handling and the documented build settings, then compare the existing NextJS deployment path with Remix's deployment requirements. Done means a Remix app can be deployed through Amplify Hosting as easily as a NextJS app; the issue does not identify files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, ci-cd, cloud, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.