justin-c-anthony
commented
1 month ago Questions for kick off:
Environment Setup
- what specific versions of Node.js, Express, and Remix we should use for compatibility?
- any additional dependencies or tools required for the setup?
Project Structure
- where should the server.js file be placed?
- Are there any conventions or best practices we should follow for organizing the backend and frontend code?
Hot Module Replacement (HMR)
- specific configurations or plugins we need to set up for React Refresh (HMR) and Remix Hot Data Revalidation?
- How should we handle state management to ensure seamless HMR?
Testing and Validation
- What testing frameworks or tools should we use to validate that changes are reflected in the browser without rebuilding?
- Are there any specific test cases or scenarios we should consider for verifying HMR and Hot Data Revalidation?
rd-huerta
Context
While setting up the frontend with Remix for #18 , we discovered that further tasks would need to be done to setup the backend using our own Express server using the quick start guide's Bring Your Own Server section rather than using Remix's built in remix-serve functionality, so that for our purposes we are able to see changes made in the backend of our app immediately reflected in our browser window.
User Story
As a developer I want to use React Refresh (Hot Module Replacement) and Remix Hot Data Revalidation So that I am able to see changes made in the backend of my app reflected immediately in my browser
Definition of Done
Acceptance Criteria
Given the Express server is setup When I make changes in the app's backend Then these changes are reflected in the browser, without needing to rebuild