Investigate Warnings During `remix vite:build` and Docker Image Build Process

[cheesea3]

Description:

During the remix vite:build process and the Docker image build process, several warnings are being logged. These warnings do not prevent the build process from succeeding, but they should be investigated to ensure they do not lead to future issues.

Details:

1. Unsupported engine warnings: During both npm install and npm run build, warnings about unsupported engines are logged. These warnings are related to the Node.js and npm versions being used. Here are some examples:

   npm WARN EBADENGINE Unsupported engine {
   npm WARN EBADENGINE   package: '@eslint/eslintrc@3.0.2',
   npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   npm WARN EBADENGINE   current: { node: 'v20.2.0', npm: '9.6.6' }
   npm WARN EBADENGINE }

2. Deprecated package warning: A warning about a deprecated package (@types/testing-library__jest-dom@6.0.0) is logged during npm install.

3. New npm version notice: A notice about a new major version of npm being available is logged after npm install.

4. Empty chunk warnings: During npm run build, several warnings about empty chunks are logged. These warnings are related to specific app files.

5. GitHub Actions Node.js version warning: An annotation warning about deprecated Node.js 16 actions is logged. The warning suggests updating to Node.js 20 actions.

Expected Outcome:

The investigation should result in a clearer understanding of these warnings and, if necessary, changes to the build process to address them. The expected outcomes are:

• Understanding why the unsupported engine warnings are being logged and how to address them.
• Understanding why the deprecated package warning is being logged and how to address it.
• Deciding whether to update to the new major version of npm.
• Understanding why the empty chunk warnings are being logged and how to address them.
• Updating the GitHub Actions to use Node.js 20 actions as suggested in the annotation warning.

Pathway:

1. Investigate the unsupported engine warnings.
2. Investigate the deprecated package warning.
3. Consider updating to the new major version of npm.
4. Investigate the empty chunk warnings.
5. Update the GitHub Actions to use Node.js 20 actions.

Future PR Commit Message:

Investigate warnings during build process